From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER EXTENSION ... UPGRADE; |
Date: | 2010-12-13 16:14:13 |
Message-ID: | 87sjy1646i.fsf@hi-media-techno.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> I see no advantage of this over a script per version combination, so
> long as you allow scripts to \include each other.
I guess the following should do:
SELECT pg_execute_sql_file('upgrade-1.sql');
But I rather prefer the 2-liner control file, myself:
upgrade-1.* = 'upgrade-1.sql'
upgrade-2.* = 'upgrade-2.sql'
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Florian Pflug | 2010-12-13 16:21:49 | Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE |
Previous Message | Tom Lane | 2010-12-13 16:12:47 | Re: SQL/MED - file_fdw |