Horton
Menu

Re: [v9.3] writable foreign tables

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Stark <stark@mit.edu>, Thom Brown <thom@linux.com>, Kohei KaiGai <kaigai@kaigai.gr.jp>, Daniel Farina <daniel@heroku.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2013-03-15T03:20:03Z
Lists: pgsql-hackers 
On Mon, Mar 11, 2013 at 3:06 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Greg Stark <stark@mit.edu> writes:
>> It feels a bit like unpredictable magic to have "DEFAULT" mean one
>> thing and omitted columns mean something else.
>
> Agreed.  The current code behaves that way, but I think that's
> indisputably a bug not behavior we want to keep.

I'm not entirely convinced that's a bug.  Both behaviors seem useful,
and there has to be some way to specify each one.

But I just work here.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix postgres_fdw's issues with inconsistent interpretation of data values.