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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Include the backend ID in the relpath of temporary relations.
Date: 2010-08-14 02:19:58
Message-ID: AANLkTimN7Ej1Fiyr1E3p+iJHbp6Mvq-ue9z71-1DJ7Qg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Fri, Aug 13, 2010 at 7:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)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 ...

No, it was the original patch that mangled that. I think the real
problem is that (1) I didn't test with dtrace enabled when writing the
patch, or maybe I did somewhere in the middle but not at the end and
(2) I didn't realize there were docs.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2010-08-14 02:22:11 pgsql: Further dtrace adjustments for the backend-IDs-in-relpath patch.
Previous Message Tom Lane 2010-08-13 23:23:14 Re: Re: [COMMITTERS] pgsql: Include the backend ID in the relpath of temporary relations.

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-08-14 02:25:45 Re: [COMMITTERS] pgsql: Recognize functional dependency on primary keys.
Previous Message James William Pye 2010-08-14 02:16:27 Re: Python 2.7 deprecated the PyCObject API?