Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] dump/reload

From: Brett McCormick <brett(at)work(dot)chicken(dot)org>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] dump/reload
Date: 1998-06-03 03:12:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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?

In response to


pgsql-hackers by date

Next:From: Brett McCormickDate: 1998-06-03 03:28:06
Subject: keeping track of connections
Previous:From: Bruce MomjianDate: 1998-06-03 02:19:01
Subject: Re: [HACKERS] dump/reload

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group