On Tue, Sep 9, 2025 at 12:07 PM Dilip Kumar wrote:
>
>
> The latest patch set is not applying on HEAD can you rebase the patch
> set. And also there are many TODOs in the patch, if those TODOs are
> just good to do and you are planning for future development better to
> get rid of those. OTOH if
On Thu, Jun 5, 2025 at 6:09 PM Nitin Motiani wrote:
>
> Hi,
>
> Apologies for the delay on this thread.
>
> On Mon, Apr 28, 2025 at 1:52 PM Nitin Motiani wrote:
> >
> > Thanks for the feedback, Thomas.
> >
> > > Do I understand correctly that
> > > the problem you encountered is in some other tes
Hi,
Went ahead and experimented with your patch a bit. To answer my previous
question this patch can be used to pipe pg_dump directly into pg_restore. This
should absolutely be added as another use case to your list above as it is a
well known limitation that you can use pg_dump/psql to do buff
Hi,
Very interesting patch. One question: is it possible with this patch to pipe
pg_dump directory output directly into pg_restore with this patch? Looking at
the code I don't believe that is the case but figured I would ask.
Thanks,
Andrew Jackson
I have added this to the commitfest
We would be grateful for any reviews and feedback on this.
When adding to commitfest I tried to put Nitin as "first author" as he
has done the bulk of the work (I did just a quick pg_dump-only PoC)
but it looks like Commitfest just orders all provided authors
a
Hi,
Apologies for the delay on this thread.
On Mon, Apr 28, 2025 at 1:52 PM Nitin Motiani wrote:
>
> Thanks for the feedback, Thomas.
>
> > Do I understand correctly that
> > the problem you encountered is in some other tests that you haven't
> > attached yet? Could you post what you have so th
Thanks for the feedback, Thomas.
> No comment on the wider project except that it looks generally useful,
> and I can see that it's not possible to use the conventional POSIX
> filename "-" to represent stdout, because you need to write to
> multiple files so you need to come up with *something* a
On Tue, Apr 8, 2025 at 7:48 AM Hannu Krosing wrote:
> Just to bring this out separately : Does anybody have any idea why pipe
> commands close inside tests ?
>
> Re: 003-pg_dump_basic_tests has a few basic validation tests for
> correctmflag combinations. We need to write more automated tests in
If there are no objections we will add this to the commitfest
On Mon, Apr 7, 2025 at 9:48 PM Hannu Krosing wrote:
>
>
> Just to bring this out separately : Does anybody have any idea why pipe
> commands close inside tests ?
>
> Re: 003-pg_dump_basic_tests has a few basic validation tests for
> c
Just to bring this out separately :
Does anybody have any ideas why pipe commands prematurely close inside tests ?
> Re: 003-pg_dump_basic_tests has a few basic validation tests for
> correctmflag combinations. We need to write more automated tests in
> 002_pg_dump.pl but have been running into
Just to bring this out separately : Does anybody have any idea why pipe
commands close inside tests ?
Re: 003-pg_dump_basic_tests has a few basic validation tests for
correctmflag combinations. We need to write more automated tests in
002_pg_dump.pl but have been running into some issues with envi
Hi Hackers,
We are proposing the ability to specify a pipe command to pg_dump by a
flag. And attaching the patch set.
Why : Currently it is quite simple to pipe the output of pg_dump for
text format to a pipe at command line and do any manipulations
necessary. Following is an example :
pg
12 matches
Mail list logo