Re: Disabling function validation - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Disabling function validation
Date
Msg-id 200310071658.h97GwOV20585@candle.pha.pa.us
Whole thread Raw
In response to Re: Disabling function validation  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Disabling function validation
Re: Disabling function validation
List pgsql-hackers
Peter Eisentraut wrote:
> Bruce Momjian writes:
> 
> > I think we should change the "check_function_bodies" to something more
> > general.  I like "restore_validation_mode" because it could also be used
> > to disable foreign key checks which we are discussing.  An even more
> > general idea would be to have something like "restore_mode", and perhaps
> > could handle cases like allowing a larger sort_mem or other
> > optimizations during restore.
> 
> I also like this approach (independent of whether foreign keys should be
> one of its applications).  It gives us more freedom to open and close
> these types of holes when new issues arise or pg_dump improves.

Should we add a variable that is set from the dump filew that identifies
the version of PostgreSQL that generated the dump?
SET dumped_version = 7.3

or something like that.  We could test it in the PostgreSQL backend code
in case we have to handle something differently.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Disabling function validation
Next
From: "Joshua D. Drake"
Date:
Subject: BigInt woes