Re: pg_dump compatibility with 7.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump compatibility with 7.0
Date: 2001-04-15 05:08:46
Message-ID: 27322.987311326@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> At the moment it has no idea what do do with aggregates (is there
> anything?), and it assumes 'proisstrict' on functions.

I'll take the blame for the aggregate issue ;-).

SFUNC1/STYPE1/INITCOND1 in 7.0 equate to SFUNC/STYPE/INITCOND in 7.1.
There is no 7.1 equivalent to 7.0's SFUNC2/STYPE2/INITCOND2 --- those
have to be saved/restored separately if you are dumping a 7.0 database
with intentions of restoring it to 7.0. On the other hand, if you are
dumping 7.0 with an eye to restoring to 7.1, you could just as well
raise an error if those fields are nonnull.

Assuming 'proisstrict' for a 7.0 function seems reasonable.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vince Vielhaber 2001-04-15 05:17:15 Fast Forward (fwd)
Previous Message The Hermit Hacker 2001-04-15 04:36:39 Re: Hey guys, check this out.