Re: use pg_get_functiondef() in pg_dump - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: use pg_get_functiondef() in pg_dump
Date
Msg-id 7efccdea-8b77-eca8-6ef6-2ef705c29c01@2ndquadrant.com
Whole thread Raw
In response to Re: use pg_get_functiondef() in pg_dump  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: use pg_get_functiondef() in pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2020-08-12 21:54, Robert Haas wrote:
> One problem with this, which I think Tom pointed out before, is that
> it might make it to handle some forward-compatibility problems. In
> other words, if something that the server is generating needs to be
> modified for compatibility with a future release, it's not easy to do
> that. Like if we needed to quote something we weren't previously
> quoting, for example.

We already use a lot of other pg_get_*def functions in pg_dump.  Does 
this one introduce any fundamentally new problems?

A hypothetical change where syntax that we accept now would no longer be 
accepted in a (near-)future version would create a lot of upsetness.  I 
don't think we'd do it.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: remove some ancient port hacks
Next
From: Dilip Kumar
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions