Postgres Pro
Downloads
Home   >   mailing lists

Re: Computer VARSIZE_ANY(PTR) during debugging - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Computer VARSIZE_ANY(PTR) during debugging
Date
Msg-id CAM-w4HPzhxiwJ-DTKgVCzHYG+hAt22UPpMp4hNAw2BqUOkZGbQ@mail.gmail.com
Whole thread Raw
In response to Re: Computer VARSIZE_ANY(PTR) during debugging  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Computer VARSIZE_ANY(PTR) during debugging
Re: Computer VARSIZE_ANY(PTR) during debugging
List pgsql-hackers
Tree view 
I think there's some magic in gdb for this but I'm not sure how to
make it happen. If you figure it out I would think it would be
generally useful and we should find a way to put it in the source tree
so it works for everyone.

You might find it useful to put breakpoints in heap_deformtuple() with
conditions that catch the tuple you're looking for. That function will
often (but not always) be the first function to see your corrupt
tuple.

pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Next
From: Josh Berkus
Date:
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])