Skip site navigation (1) Skip section navigation (2)

Re: pgsql: TABLE command

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: TABLE command
Date: 2008-11-20 22:26:23
Message-ID: 15178.1227219983@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
petere(at)postgresql(dot)org (Peter Eisentraut) writes:
> Log Message:
> -----------
> TABLE command

If this got re-posted for review I missed it :-(.  I disagree with using
qualified_name here --- I think it would be better to use relation_expr
so that people would have the ability to specify inheritance behavior.
If you want to point to the spec and say that that syntax isn't in the
spec, that's true, but then you need to justify the inhOpt setting
you're forcing people to use.  It's not entirely clear what behavior the
spec intends, but I'm pretty sure INH_DEFAULT isn't it.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2008-11-20 23:44:22
Subject: Re: Cool hack with recursive queries
Previous:From: Kenneth MarshallDate: 2008-11-20 22:06:56
Subject: Re: WIP parallel restore patch

pgsql-committers by date

Next:From: Bruce MomjianDate: 2008-11-21 00:43:16
Subject: Re: pgsql: Fix some issues that prevent this file to be processed by
Previous:From: Magnus HaganderDate: 2008-11-20 21:27:13
Subject: Re: Re: [COMMITTERS] pgsql: Silence compiler warning about ignored return value.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group