Re: Assorted improvements in pg_dump - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Assorted improvements in pg_dump
Date
Msg-id 20211025213550.2gd35lum5duw7urk@alap3.anarazel.de
Whole thread Raw
In response to Re: Assorted improvements in pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Assorted improvements in pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2021-10-25 16:02:34 -0400, Tom Lane wrote:
> So I'd like a better idea, but I'm not sure that that one is better.

I guess we could move the prepared-statement handling into a query execution
helper. That could then use a hashtable or something similar to check if a
certain prepared statement already exists. That'd then centrally be extensible
to deal with multiple connects etc.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: Allow pg_signal_backend members to use pg_log_backend_memory_stats().
Next
From: Alvaro Herrera
Date:
Subject: Re: Refactoring: join MakeSingleTupleTableSlot() and MakeTupleTableSlot()