Re: binary array and record recv

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Andrew Chernow <ac(at)esilo(dot)com>
Subject: Re: binary array and record recv
Date: 2009-01-27 15:30:30
Message-ID: 20090127153030.GH6444@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > On Tuesday 18 December 2007 18:30:22 Tom Lane wrote:
> >> Arguably, pg_dump from an older version should make sure that the auto
> >> rules should NOT get created, else it is failing to preserve an older
> >> view's behavior.
>
> > We extend properties of objects all the time. That is why we make new
> > releases. No one is required to use the new properties.
>
> > Should pg_dump also make sure that tables imported from an older version are
> > not usable for recursive unions or window functions, thus preserving the
> > older table's behavior?
>
> That argument seems fairly bogus. The addition of those features won't
> change the behavior of existing applications.

How will adding updatable views change them? The only change is that
when you try to insert/update/delete on a view, it used to give an
error, but the new version will accept it. How can this be a problem?
Surely no application is depending on the fact that this will raise an
error.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-01-27 15:33:08 Re: Commitfest infrastructure (was Re: 8.4 release planning)
Previous Message Andrew Dunstan 2009-01-27 15:30:10 Re: mingw check hung