Re: pg_dump versus defaults on foreign tables

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump versus defaults on foreign tables
Date: 2013-05-15 20:57:23
Message-ID: 5193F6B3.3010802@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

> Comments?

I personally think that FOREIGN should be optional on most commands
where ambiguity is unlikely. In addition to ALTER, there's no
particularly good reason why "DROP TABLE myforeigntable" doesn't work.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-05-15 21:18:06 Re: Heap truncation without AccessExclusiveLock (9.4)
Previous Message Tom Lane 2013-05-15 20:34:07 pg_dump versus defaults on foreign tables