Re: pg_dump versus defaults on foreign tables - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: pg_dump versus defaults on foreign tables
Date
Msg-id 5193F6B3.3010802@agliodbs.com
Whole thread Raw
In response to pg_dump versus defaults on foreign tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump versus defaults on foreign tables  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: pg_dump versus defaults on foreign tables
Next
From: Robert Haas
Date:
Subject: Re: Heap truncation without AccessExclusiveLock (9.4)