| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com> |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Optimize LISTEN/NOTIFY |
| Date: | 2025-10-07 16:51:20 |
| Message-ID: | 2451053.1759855880@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Matheus Alcantara <matheusssilv97(at)gmail(dot)com> writes:
> 7. I'm wondering if we could add some TAP tests for this?
async.c seems already moderately well covered by existing tests
src/test/regress/sql/async.sql
src/test/isolation/specs/async-notify.spec
Do we need more? If there's something not covered, can we extend
those test cases instead of spinning up a whole new installation
for a TAP test?
Also, I don't think it's the job of this patch to provide test
coverage for dshash. That should be quite well covered already.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shayon Mukherjee | 2025-10-07 16:54:07 | Proposal for discussions: Allow reads to proceed during FK/trigger drops by reducing relation-level lock from AccessExclusive to ShareRowExclusive |
| Previous Message | Matthias van de Meent | 2025-10-07 16:40:48 | Re: Buffer locking is special (hints, checksums, AIO writes) |