Re: [PATCH] pg_dump: lock tables in batches - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] pg_dump: lock tables in batches
Date
Msg-id 4029125.1670427873@sss.pgh.pa.us
Whole thread Raw
In response to [PATCH] pg_dump: lock tables in batches  (Aleksander Alekseev <aleksander@timescale.com>)
Responses Re: [PATCH] pg_dump: lock tables in batches  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Aleksander Alekseev <aleksander@timescale.com> writes:
> What he proposes is taking the locks in batches.

I have a strong sense of deja vu here.  I'm pretty sure I experimented
with this idea last year and gave up on it.  I don't recall exactly
why, but either it didn't show any meaningful performance improvement
for me or there was some actual downside (that I'm not remembering
right now).

This would've been in the leadup to 989596152 and adjacent commits.
I took a quick look through the threads cited in those commit messages
and didn't find anything about it, but I think the discussion had
gotten scattered across more threads.  Some digging in the archives
could be useful.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Error-safe user functions
Next
From: "David G. Johnston"
Date:
Subject: Re: Error-safe user functions