On Wed, Sep 3, 2014 at 12:07:55PM -0400, Bruce Momjian wrote:
On Mon, Sep 1, 2014 at 04:40:11PM -0400, Bruce Momjian wrote:
On Mon, Sep 1, 2014 at 04:06:58PM -0400, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
NOTICE: moving and merging column c with inherited
On Mon, Sep 1, 2014 at 04:40:11PM -0400, Bruce Momjian wrote:
On Mon, Sep 1, 2014 at 04:06:58PM -0400, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
NOTICE: moving and merging column c with inherited definition
DETAIL: user-specified column moved to the location of the
On Sun, Aug 31, 2014 at 02:10:33PM -0400, Tom Lane wrote:
David G Johnston david.g.johns...@gmail.com writes:
Would it be proper to issue an additional top-level warning with the column
moved notification? Thus there would be NOTICE, NOTICE, WARNING in the
above example? Or, more
Bruce Momjian br...@momjian.us writes:
NOTICE: moving and merging column c with inherited definition
DETAIL: user-specified column moved to the location of the inherited
column
Dept of nitpicking: errdetail messages are supposed to be complete
sentences, properly
On Mon, Sep 1, 2014 at 04:06:58PM -0400, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
NOTICE: moving and merging column c with inherited definition
DETAIL: user-specified column moved to the location of the inherited
column
Dept of nitpicking: errdetail messages
On Sat, Aug 30, 2014 at 07:32:26PM -0400, Bruce Momjian wrote:
On Wed, Aug 27, 2014 at 09:40:30PM -0400, Noah Misch wrote:
3. use the pg_dump binary-upgrade code when such cases happen
+1. We have the convention that, while --binary-upgrade can inject catalog
hacks, regular pg_dump
Bruce Momjian br...@momjian.us writes:
I have developed the attached patch to warn about column reordering in
this odd case. The patch mentions the reordering of c:
NOTICE: merging column a with inherited definition
NOTICE: merging column c with inherited definition; column
Tom Lane-2 wrote
Bruce Momjian lt;
bruce@
gt; writes:
I have developed the attached patch to warn about column reordering in
this odd case. The patch mentions the reordering of c:
NOTICE: merging column a with inherited definition
NOTICE: merging column c with inherited
David G Johnston david.g.johns...@gmail.com writes:
Would it be proper to issue an additional top-level warning with the column
moved notification? Thus there would be NOTICE, NOTICE, WARNING in the
above example? Or, more generically, columns reordered to match inherited
column order to
On Wed, Aug 27, 2014 at 09:40:30PM -0400, Noah Misch wrote:
3. use the pg_dump binary-upgrade code when such cases happen
+1. We have the convention that, while --binary-upgrade can inject catalog
hacks, regular pg_dump uses standard, documented DDL. I like that convention
on general
On Mon, Mar 17, 2014 at 07:12:12PM -0400, Noah Misch wrote:
On Fri, Mar 14, 2014 at 12:33:04PM -0300, Alvaro Herrera wrote:
Tom Lane wrote:
Alvaro Herrera alvhe...@2ndquadrant.com writes:
I wonder if the real fix here is to have ALTER / INHERIT error out of
the columns in B are not a
On Wed, Aug 27, 2014 at 11:24:53AM -0400, Tom Lane wrote:
On Wed, Aug 27, 2014 at 10:40:53AM -0400, Bruce Momjian wrote:
I looked at this issue from March and I think we need to do something.
In summary, the problem is that tables using inheritance can be dumped
and reloaded with columns
12 matches
Mail list logo
