On Fri, Jul 5, 2019 at 1:14 PM Corey Huinker wrote:
> I'd like to hear what others have to say, and incorporate that feedback into
> a follow up proposal.
I am unclear how this could be implemented without ending up with a
ton of extra code that has to be maintained. pg_dump is a client-side
On Sat, Jul 13, 2019 at 06:32:41PM -0500, Michael Glaesemann wrote:
>
>
> > On 2019–07–05, at 12:14, Corey Huinker wrote:
> >
> > In doing that work, it became clear that the command was serving two
> > masters:
> > 1. A desire to see the underlying nuts and bolts of a given database object.
> On 2019–07–05, at 12:14, Corey Huinker wrote:
>
> In doing that work, it became clear that the command was serving two masters:
> 1. A desire to see the underlying nuts and bolts of a given database object.
> 2. A desire to essentially make the schema portion of pg_dump a server side
>
On Fri, Jul 5, 2019 at 12:32 PM David Fetter wrote:
> Folks,
>
> Corey Huinker put together the documentation for this proposed
> feature. Does this seem like a reasonable way to do it?
>
>
In doing that work, it became clear that the command was serving two
masters:
1. A desire to see the
