From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: dshash: Add sequential scan support. |
Date: | 2022-03-11 01:02:51 |
Message-ID: | E1nSTgB-000BxB-4B@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
dshash: Add sequential scan support.
Add ability to scan all entries sequentially to dshash. The interface is
similar but a bit different both from that of dynahash and simple dshash
search functions. The most significant differences is that dshash's interfac
always needs a call to dshash_seq_term when scan ends. Another is
locking. Dshash holds partition lock when returning an entry,
dshash_seq_next() also holds lock when returning an entry but callers
shouldn't release it, since the lock is essential to continue a scan. The
seqscan interface allows entry deletion while a scan is in progress using
dshash_delete_current().
Reviewed-By: Andres Freund <andres(at)anarazel(dot)de>
Author: Kyotaro Horiguchi <horikyoga(dot)ntt(at)gmail(dot)com>
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/352d297dc74feb0bf0dcb255cc0dfaaed2b96c1e
Modified Files
--------------
src/backend/lib/dshash.c | 163 ++++++++++++++++++++++++++++++++++++++-
src/include/lib/dshash.h | 23 ++++++
src/tools/pgindent/typedefs.list | 1 +
3 files changed, 186 insertions(+), 1 deletion(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-03-11 01:09:56 | Re: pgsql: dshash: Add sequential scan support. |
Previous Message | Peter Eisentraut | 2022-03-10 13:16:11 | pgsql: Re-update Unicode data to CLDR 39 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-03-11 01:09:56 | Re: pgsql: dshash: Add sequential scan support. |
Previous Message | Justin Pryzby | 2022-03-11 01:02:23 | Re: refactoring basebackup.c |