Re: Re: [COMMITTERS] pgsql: Include the backend ID in the relpath of temporary relations. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Include the backend ID in the relpath of temporary relations.
Date
Msg-id 24817.1281741794@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Include the backend ID in the relpath of temporary relations.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Re: [COMMITTERS] pgsql: Include the backend ID in the relpath of temporary relations.
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> I have taken a crack at fixing this but someone who understands DTrace
> better than I do may want to check and see if the changes look sane.
> It appears to me that we have no documentation - not even so much as a
> source code comment - explaining how these probes are supposed to work
> or what the arguments to each one are intended mean.

http://developer.postgresql.org/pgdocs/postgres/dynamic-trace.html#DTRACE-PROBE-POINT-TABLE

(... which you now need to update ...)

I think your confusion may stem from the fact that the definition of the
buffer-read-done probe was actually wrong, AFAICS.  The docs say its
last 3 args were bools, which was reasonable, but the definition said
int for the first of those.  Which is what you want now ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Include the backend ID in the relpath of temporary relations.
Next
From: Tom Lane
Date:
Subject: Python 2.7 deprecated the PyCObject API?