Re: new heapcheck contrib module - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: new heapcheck contrib module
Date
Msg-id 70655DF3-33CE-4527-9A4D-DDEB582B6BA0@enterprisedb.com
Whole thread Raw
In response to Re: new heapcheck contrib module  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: new heapcheck contrib module  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers

> On Jan 31, 2021, at 4:05 PM, Mark Dilger <mark.dilger@enterprisedb.com> wrote:
>
> Attached is patch set 35.

I found some things to improve in the v35 patch set.  Please find attached the v36 patch set, which differs from v35 in
thefollowing ways: 

0001 -- no changes

0002 -- fixing omissions in @pgfeutilsfiles in file src/tools/msvc/Mkvcbuild.pm

0003 -- no changes

0004:
  -- Fixes handling of amcheck contrib module installed in non-default schema.
  -- Adds database name to corruption messages to make identifying the relation being complained about unambiguous in
multi-databasechecks 
  -- Fixes an instance where pg_amcheck was querying pg_database without schema-qualifying it
  -- Simplifying some functions in pg_amcheck.c
  -- Updating a comment to reflect the renaming of a variable that the comment mentioned by name

0005 -- fixes =pod added in PostgresNode.pm.  The =pod was grammatically correct so far I can tell, but rendered
strangelyin perldoc. 




—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company




Attachment

pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Proposal: Save user's original authenticated identity for logging
Next
From: Alvaro Herrera
Date:
Subject: Re: LogwrtResult contended spinlock