On 2018-Jul-13, amul sul wrote:
> Thanks for the prompt fix, patch [1] works for me.
>
> 1] https://postgr.es/m/20180712184537.5vjwgxlbuiomomqd@alvherre.pgsql
Thanks for checking, pushed.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remot
Thanks for the prompt fix, patch [1] works for me.
1] https://postgr.es/m/20180712184537.5vjwgxlbuiomomqd@alvherre.pgsql
Regards,
Amul
On Thu, Jul 12, 2018 at 11:34:43PM -0400, Alvaro Herrera wrote:
> I'm not sure what to *do* with the partition, though :-) I don't think
> there's a nice way to verify that the FK actually exists, or that
> catalog rows are set in such-and-such way, after restoring this.
> The pg_restore tests are
On 2018-Jul-13, Michael Paquier wrote:
> On Thu, Jul 12, 2018 at 02:45:37PM -0400, Alvaro Herrera wrote:
> > Thanks, looks good. I propose to add following pg_dump test to ensure
> > this stays fixed.
>
> Thanks for adding the test. I was looking at a good way to add a test
> but could not come
On Thu, Jul 12, 2018 at 02:45:37PM -0400, Alvaro Herrera wrote:
> Thanks, looks good. I propose to add following pg_dump test to ensure
> this stays fixed.
Thanks for adding the test. I was looking at a good way to add a test
but could not come up with something which can be summed up with one
q
On 2018-Jul-12, Michael Paquier wrote:
> Changing pg_class.relhastriggers is out of scope because as far as I
> know partitioned tables have no triggers, so the current value is
> correct, and that would be a catalog change at this stage which would
> cause any existing deployments of v11 to compl
On 2018-Jul-12, Michael Paquier wrote:
> On Wed, Jul 11, 2018 at 03:49:59PM +0530, amul sul wrote:
> > On the master head, getConstraints() function skips FK constraints for
> > a partitioned table because of tbinfo->hastriggers is false.
> >
> > While creating FK constraints on the partitioned t
On Wed, Jul 11, 2018 at 03:49:59PM +0530, amul sul wrote:
> On the master head, getConstraints() function skips FK constraints for
> a partitioned table because of tbinfo->hastriggers is false.
>
> While creating FK constraints on the partitioned table, the FK triggers are
> only
> created on lea
