On Tue, 2 June 1998, at 22:19:01, Bruce Momjian wrote:
> > they don't always work, in the case of a table with an attribute that
> > calls a function for its default value.
> This is a good point, and something worth thinking about. Maybe we
> could scan through the defaults for a table, and call the dumpfunction
> command for any functions. Then when they are later attempted to be
> created, they would fail, or we could somehow mark them as already
> dumped.
Would we look at the binary plan (aiee!) or just try and parse the
string value 'pg_attdef.adsrc` for a function call?