On Wed, Aug 22, 2012 at 12:59 PM, Jeff Davis davis.jeff...@gmail.com wrote:
On Tue, 2012-08-21 at 10:41 -0400, Robert Haas wrote:
The thing to keep in mind here is that EVERY property of a foreign
table is subject to change at any arbitrary point in time, without our
knowledge. ... Why should
On Tue, 2012-08-21 at 10:41 -0400, Robert Haas wrote:
The thing to keep in mind here is that EVERY property of a foreign
table is subject to change at any arbitrary point in time, without our
knowledge. ... Why should CHECK constraints be any different than,
say, column types?
So, let's say
On Mon, Aug 20, 2012 at 5:14 PM, Jeff Davis pg...@j-davis.com wrote:
On Mon, 2012-08-20 at 16:50 -0400, Robert Haas wrote:
#3 for foreign tables.
I'm skeptical of that approach for two reasons:
(1) It will be hard to inform users which constraints are enforced and
which aren't.
The thing
On Fri, Aug 17, 2012 at 4:08 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Excerpts from Robert Haas's message of vie ago 17 15:44:29 -0400 2012:
On Fri, Aug 17, 2012 at 2:58 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I mean, what are NOT NULL in foreign tables for? Are they
On Fri, 2012-08-17 at 15:44 -0400, Robert Haas wrote:
On Fri, Aug 17, 2012 at 2:58 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I mean, what are NOT NULL in foreign tables for? Are they harmed or
helped by having pg_constraint rows?
As I've mentioned when this has come up before, I
On Mon, Aug 20, 2012 at 3:56 PM, Jeff Davis pg...@j-davis.com wrote:
On Fri, 2012-08-17 at 15:44 -0400, Robert Haas wrote:
On Fri, Aug 17, 2012 at 2:58 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I mean, what are NOT NULL in foreign tables for? Are they harmed or
helped by having
On Mon, 2012-08-20 at 16:50 -0400, Robert Haas wrote:
#3 for foreign tables.
I'm skeptical of that approach for two reasons:
(1) It will be hard to inform users which constraints are enforced and
which aren't.
(2) It will be hard for users to understand the planner benefits or the
consequences
Hi,
I noticed one more problem with NOT NULL constraints and foreign tables
-- which is that they are allowed at all (see also
http://archives.postgresql.org/message-id/1345214955-sup-3...@alvh.no-ip.org
earlier today).
Right now, with my patch, foreign table creation fails if you have a NOT
Alvaro Herrera alvhe...@2ndquadrant.com writes:
I mean, what are NOT NULL in foreign tables for?
There was previous discussion about that, in the context of check
constraints in general, but I don't believe we reached consensus.
On Fri, Aug 17, 2012 at 2:58 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I mean, what are NOT NULL in foreign tables for? Are they harmed or
helped by having pg_constraint rows?
As I've mentioned when this has come up before, I think that
constraints on foreign tables should be viewed
Excerpts from Robert Haas's message of vie ago 17 15:44:29 -0400 2012:
On Fri, Aug 17, 2012 at 2:58 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I mean, what are NOT NULL in foreign tables for? Are they harmed or
helped by having pg_constraint rows?
As I've mentioned when this has
On 17-08-2012 16:44, Robert Haas wrote:
On Fri, Aug 17, 2012 at 2:58 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I mean, what are NOT NULL in foreign tables for? Are they harmed or
helped by having pg_constraint rows?
As I've mentioned when this has come up before, I think that
12 matches
Mail list logo
