Re: pgsql: Add note that inlined SQL functions aren't tracked by

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add note that inlined SQL functions aren't tracked by
Date: 2009-02-23 14:56:12
Message-ID: 3351.1235400972@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On Sun, 2009-02-22 at 23:50 +0000, Tom Lane wrote:
>> Log Message:
>> -----------
>> Add note that inlined SQL functions aren't tracked by track_functions.

> How will users tell which functions they are?

They're the ones that don't get tracked ;-)

The wording of the note does give a hint that they have to be "simple".
I thought about going into more detail but decided that that wouldn't be
appropriate in a marginal note --- the full rules would take paragraphs
to explain, and tend to change from release to release anyway. I think
setting expectations is sufficient here.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-02-23 15:59:55 pgsql: Fix psql's \dD to show only one row per domain, even when the
Previous Message User Bmomjian 2009-02-23 14:02:13 pg-migrator - src: Use assert rather than Assert because we don't link