From: | Dave Johansen <davejohansen(at)gmail(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | NO INHERIT and prepared statements? |
Date: | 2016-05-19 19:42:26 |
Message-ID: | CAAcYxUc+eFypfE0g-WtRriwMHK1zBH3xX-qowhSROq5m_uVZYA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
We have a time-based partitioning scheme and with Postgres 8.4 on RHEL 6 we
would "detach" a partition that was no longer being written to and CLUSTER
it before "re-attaching" it [1]. This never seemed to have any issues, but
we recently upgraded to Postgres 9.2 on RHEL 7 and we've noticed a few
instances where prepared statements fail and it appears to be caused by
running NO INHERIT to "detach" the partition that is no longer being
written to. Is this an issue caused by the changes in the planner in
regards to how prepared statements are handled [2]?
Thanks,
Dave
[1]
http://www.postgresql.org/message-id/CAAcYxUcZRzfq3RPXEkuRFgqduiRaFA2RgTaHkPBTizZZhmZRwA@mail.gmail.com
[2]
https://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.2#Performance_improvements
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Hancock | 2016-05-19 23:11:24 | read-only remote replica |
Previous Message | David G. Johnston | 2016-05-19 19:10:41 | Re: canceling a delete |