Re: pg_dump versus defaults on foreign tables

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump versus defaults on foreign tables
Date: 2013-05-15 23:08:16
Message-ID: 51941560.6000708@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> In any case, that restriction isn't breaking pg_dump so I don't feel
> a need to change it during beta.

Sure. Maybe put it on the stack for 9.4.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-05-15 23:10:16 Re: Heap truncation without AccessExclusiveLock (9.4)
Previous Message Josh Berkus 2013-05-15 22:53:24 Re: "on existing update" construct