Re: Avoiding upgrade backlash

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-advocacy(at)postgresql(dot)org, josh(at)agliodbs(dot)com, pgsql-docs(at)postgresql(dot)org
Subject: Re: Avoiding upgrade backlash
Date: 2007-11-13 16:38:50
Message-ID: 9AA942690F2E0B8A997D26F1@imhotep.credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-docs

--On Dienstag, November 13, 2007 11:05:18 +0100 Stefan Kaltenbrunner
<stefan(at)kaltenbrunner(dot)cc> wrote:

>> What difference would pg_dump make?
>
> well the current problem is that either way pg_dump can generate dumps
> that are not restorable without modification on 8.3 (like say one that
> contains a VIEW that does a INTEGER = TEXT comparision which 8.3 will
> refuse to create) even if dumped with 8.3.

AFAIK pg_dump and its related dump routines takes care to dump this in a
proper way with explicit casts attached. Do you have an example showing a
possible misbehavior?

--
Thanks

Bernd

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Tom Lane 2007-11-13 16:39:26 Re: [DOCS] Avoiding upgrade backlash
Previous Message Peter Eisentraut 2007-11-13 16:34:54 Re: [pgsql-advocacy] Avoiding upgrade backlash

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2007-11-13 16:39:26 Re: [DOCS] Avoiding upgrade backlash
Previous Message Peter Eisentraut 2007-11-13 16:34:54 Re: [pgsql-advocacy] Avoiding upgrade backlash