Re: pg_dump vs. TRANSFORMs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump vs. TRANSFORMs
Date
Msg-id 7183.1481230828@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump vs. TRANSFORMs  (Stephen Frost <sfrost@snowman.net>)
Responses Re: pg_dump vs. TRANSFORMs  (Stephen Frost <sfrost@snowman.net>)
Re: [HACKERS] pg_dump vs. TRANSFORMs  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> Ok, thinking a bit more on this and testing, it looks like we record the
> initdb-defined casts as 'pinned' in pg_depend all the way back to 7.3.
> Therefore, we could use that as the gating factor for getFuncs() instead
> of FirstNormalObjectId and then I can also modify getCasts() to exclude
> pinned casts, which should fix pg_dump against 8.0 and earlier.

Don't really like that; won't it make the getFuncs query substantially
more expensive?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Typmod associated with multi-row VALUES constructs
Next
From: Tom Lane
Date:
Subject: Re: tuplesort_gettuple_common() and *should_free argument