Re: pg9.6 segfault using simple query (related to use fk for join estimates)
От | Robert Haas |
---|---|
Тема | Re: pg9.6 segfault using simple query (related to use fk for join estimates) |
Дата | |
Msg-id | CA+TgmoavPp9Xdo-DG1v8W0o+0GJwtevMqcEdh6WoT39ggv0oSg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg9.6 segfault using simple query (related to use fk for join estimates) (Noah Misch <noah@leadboat.com>) |
Ответы |
Re: pg9.6 segfault using simple query (related to use fk for join
estimates)
Re: pg9.6 segfault using simple query (related to use fk for join estimates) Re: pg9.6 segfault using simple query (related to use fk for join estimates) |
Список | pgsql-hackers |
On Wed, Jun 1, 2016 at 9:29 PM, Noah Misch <noah@leadboat.com> wrote: > This PostgreSQL 9.6 open item is past due for your status update. Kindly send > a status update within 24 hours, and include a date for your subsequent status > update. Refer to the policy on open item ownership: > http://www.postgresql.org/message-id/20160527025039.GA447393@tornado.leadboat.com FYI, I spoke to Tom Lane about this at PGCon and suggested that he look at the proposed patch as I requested in https://www.postgresql.org/message-id/CA+TgmobPqrAVXOBMHTcpDq8hX7gCzcVhoUvC8s9V=d09+bt30w@mail.gmail.com and see whether that would address his concerns, and he said that he would do that. It may, however, have slipped his mind. My opinion is that something needs to be done about this patch. It needs to be improved or reverted. Improved would be ideal in my mind, but reverted is an outcome I can live with. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: