Re: pg_dump compatibility with 7.0 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump compatibility with 7.0
Date
Msg-id 27322.987311326@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump compatibility with 7.0  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: pg_dump compatibility with 7.0  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
Philip Warner <pjw@rhyme.com.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


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: Hey guys, check this out.
Next
From: Vince Vielhaber
Date:
Subject: Fast Forward (fwd)