On Tue, Jun 4, 2024 at 3:15 PM Ron Johnson wrote:
>
> But why tar instead of custom? That was part of my original question.
>
I've found it pretty useful for programmatically accessing data in a dump
for large databases outside of the normal pg_dump/pg_restore workflow. You
don't have to seek th
On Tue, Jun 4, 2024 at 7:36 PM Ron Johnson wrote:
> On Tue, Jun 4, 2024 at 3:47 PM Gavin Roy wrote:
>
>>
>> On Tue, Jun 4, 2024 at 3:15 PM Ron Johnson
>> wrote:
>>
>>>
>>> But why tar instead of custom? That was part of my original que
Hi All,
My team was testing against Postgres 14 to ensure we could cleanly upgrade
and we ran across a regression in our PL/PGSQL code related to the updates
to RETURN QUERY.
Our code which works in previous versions of Postgres uses UPDATE RETURNING
and INSERT RETURNING in combination with RETUR
On Thu, Oct 7, 2021 at 2:54 PM Adrian Klaver
wrote:
> On 10/7/21 11:38 AM, Gavin Roy wrote:
> > Hi All,
> >
> > My team was testing against Postgres 14 to ensure we could cleanly
> > upgrade and we ran across a regression in our PL/PGSQL code related to
>
Thanks so much Tom!
Regards,
Gavin
On Thu, Oct 7, 2021 at 3:05 PM Tom Lane wrote:
> Gavin Roy writes:
> > Our code which works in previous versions of Postgres uses UPDATE
> RETURNING
> > and INSERT RETURNING in combination with RETURN QUERY. It appears that in
> >
On Wed, Nov 24, 2021 at 2:15 PM Godfrin, Philippe E <
philippe.godf...@nov.com> wrote:
> Greetings
>
> I am inserting a large number of rows, 5,10, 15 million. The python code
> commits every 5000 inserts. The table has partitioned children.
>
On the Python client side, if you're using psycopg, y
