Request a Demo
Home   >   mailing lists

Re: Optimize LISTEN/NOTIFY - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Optimize LISTEN/NOTIFY
Date
Msg-id 2451053.1759855880@sss.pgh.pa.us
Whole thread Raw
In response to Re: Optimize LISTEN/NOTIFY  (Matheus Alcantara <matheusssilv97@gmail.com>)
Responses Re: Optimize LISTEN/NOTIFY
List pgsql-hackers
Tree view 
Matheus Alcantara <matheusssilv97@gmail.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

pgsql-hackers by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: Buffer locking is special (hints, checksums, AIO writes)
Next
From: Shayon Mukherjee
Date:
Subject: Proposal for discussions: Allow reads to proceed during FK/trigger drops by reducing relation-level lock from AccessExclusive to ShareRowExclusive