Re: proposal: possibility to read dumped table's name from file - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: proposal: possibility to read dumped table's name from file
Date
Msg-id ZBnN9x71hH8F/LQv@telsasoft.com
Whole thread Raw
In response to Re: proposal: possibility to read dumped table's name from file  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: possibility to read dumped table's name from file  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: proposal: possibility to read dumped table's name from file  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Mon, Mar 20, 2023 at 08:01:13AM +0100, Pavel Stehule wrote:
> ne 19. 3. 2023 v 15:01 odesílatel Justin Pryzby <pryzby@telsasoft.com> napsal:
> 
> > On Thu, Mar 16, 2023 at 01:05:41PM +0100, Pavel Stehule wrote:
> > > rebase + enhancing about related option from a563c24
> >
> > Thanks.
> >
> > It looks like this doesn't currently handle extensions, which were added
> > at 6568cef26e.

What about this part ?  Should extension filters be supported ?

I think the comment that I'd patched that lists all the filter types
should be minimized, rather than duplicating the list of all the
possible filters that's already in the usrr-facing documentation.

One new typo: childrent



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Making the initial and maximum DSA segment sizes configurable
Next
From: Christoph Berg
Date:
Subject: Re: Make EXPLAIN generate a generic plan for a parameterized query