On Fri, Aug 17, 2012 at 10:53 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
However I'm wondering if it'd be better to tweak the code to explicitely
check for SERIAL/BIGSERIAL instead of letting it error out in internal
conditions. The way it currently is, it seems a bit user-unfriendly
Hi,
While working on the NOT NULL constraint stuff, I noticed that if you're
creating a foreign table with a SERIAL column, it bleats like this:
CREATE FOREIGN TABLE ft1 (c1 serial) SERVER sc;
ERROR: default values on foreign tables are not supported
Note that it's talking about a default
