Re: proposal - plpgsql unique statement id

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal - plpgsql unique statement id
Date: 2019-01-25 05:35:11
Message-ID: CAFj8pRAS2nbBJEJed-qiuzEce+-WO4Z1wb08To7Xv12Qh1Nzaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

čt 24. 1. 2019 v 23:08 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:

> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> > committed
>
> Why didn't this patch modify the dumping logic in pl_funcs.c to print
> the IDs? I'm not aware of other cases where we intentionally omit
> fields from debug-support printouts.
>

I had not a idea, so this field can be useful there. I'll send a patch with
it.

Regards

Pavel

> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2019-01-25 05:45:20 Re: PostgreSQL vs SQL/XML Standards
Previous Message Edmund Horner 2019-01-25 05:02:29 Use zero for nullness estimates of system attributes