CREATE FUNCTION .. SET vs. pg_dump

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: CREATE FUNCTION .. SET vs. pg_dump
Date: 2013-08-18 11:05:04
Message-ID: 5210AA60.4030306@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi all!

While working on upgrading the database of the search system on
postgresql.org to 9.2 I noticed that the dumps that pg_dump generates on
that system are actually invalid and cannot be reloaded without being
hacked on manually...

Simple way to reproduce is using the following:

CREATE TEXT SEARCH CONFIGURATION pg (
PARSER = pg_catalog."default" );

CREATE FUNCTION test() RETURNS INTEGER
LANGUAGE sql SET default_text_search_config TO 'public.pg' AS $$
SELECT 1;
$$;

once you dump that you will end up with an invalid dump because the
function will be dumped before the actual text search configuration is
(re)created. I have not checked in any more detail but I suspect that
this problem is not only affecting default_text_search_config.

Stefan

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2013-08-18 11:34:30 Re: Feature Request on Extensions
Previous Message Hannu Krosing 2013-08-18 09:36:51 Re: Feature Request on Extensions