Re: Add FOREIGN to ALTER TABLE in pg_dump - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Add FOREIGN to ALTER TABLE in pg_dump
Date
Msg-id 20200113153638.GA17031@alvherre.pgsql
Whole thread Raw
In response to Re: Add FOREIGN to ALTER TABLE in pg_dump  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
On 2020-Jan-11, Tomas Vondra wrote:

> Hi,
> 
> On Thu, Sep 26, 2019 at 01:47:28PM +0000, Luis Carril wrote:
> > 
> > I don't disagree with adding FOREIGN, though.
> > 
> > Your patch is failing the pg_dump TAP tests.  Please use
> > configure --enable-tap-tests, fix the problems, then resubmit.
> > 
> > Fixed, I've attached a new version.
> 
> This seems like a fairly small and non-controversial patch (I agree with
> Alvaro that having the optional FOREIGN seems won't hurt). So barring
> objections I'll polish it a bit and push sometime next week.

If we're messing with that code, we may as well reduce cognitive load a
little bit and unify all those multiple consecutive appendStringInfo
calls into one.  (My guess is that this was previously not possible
because there were multiple fmtId() calls in the argument list, but
that's no longer the case.)

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Krasiyan Andreev
Date:
Subject: Re: [PATCH] distinct aggregates within a window function WIP
Next
From: Kohei KaiGai
Date:
Subject: Re: How to retain lesser paths at add_path()?