Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-04-04 Thread Pavel Stehule
út 4. 4. 2023 v 19:34 odesílatel Tom Lane napsal: > Pavel Stehule writes: > > út 4. 4. 2023 v 16:20 odesílatel Tom Lane napsal: > >> If we do that, then the confusion you were concerned about upthread > >> goes away and we could shorten the keyword back down to > "pg_routine_oid", > >> which se

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-04-04 Thread Tom Lane
Pavel Stehule writes: > út 4. 4. 2023 v 16:20 odesílatel Tom Lane napsal: >> If we do that, then the confusion you were concerned about upthread >> goes away and we could shorten the keyword back down to "pg_routine_oid", >> which seems like a good thing for our carpal tunnels. > has sense OK,

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-04-04 Thread Pavel Stehule
út 4. 4. 2023 v 16:20 odesílatel Tom Lane napsal: > Pavel Stehule writes: > > There is reduced patch + regress tests > > One more thing: I do not think it's appropriate to allow this in > GET STACKED DIAGNOSTICS. That's about reporting the place where > an error occurred, not the current locati

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-04-04 Thread Tom Lane
Pavel Stehule writes: > There is reduced patch + regress tests One more thing: I do not think it's appropriate to allow this in GET STACKED DIAGNOSTICS. That's about reporting the place where an error occurred, not the current location. Eventually it might be interesting to retrieve the OID of

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-04-03 Thread Pavel Stehule
Hi po 3. 4. 2023 v 19:37 odesílatel Tom Lane napsal: > Pavel Stehule writes: > > po 27. 3. 2023 v 5:36 odesílatel Kirk Wolak napsal: > >> I have marked the item Ready for Commiter... > > > Thank you for doc and for review > > I'm kind of surprised there was any interest in this proposal at al

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-04-03 Thread Tom Lane
Pavel Stehule writes: > po 27. 3. 2023 v 5:36 odesílatel Kirk Wolak napsal: >> I have marked the item Ready for Commiter... > Thank you for doc and for review I'm kind of surprised there was any interest in this proposal at all, TBH, but apparently there is some. Still, I think you over-engine

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-03-26 Thread Pavel Stehule
Hi po 27. 3. 2023 v 5:36 odesílatel Kirk Wolak napsal: > On Sun, Mar 26, 2023 at 5:37 PM Kirk Wolak wrote: > >> On Wed, Feb 8, 2023 at 10:56 AM Kirk Wolak wrote: >> >>> On Wed, Feb 8, 2023 at 3:08 AM Pavel Stehule >>> wrote: >>> hi st 8. 2. 2023 v 7:33 odesílatel Julien Rouhau

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-03-26 Thread Kirk Wolak
On Sun, Mar 26, 2023 at 5:37 PM Kirk Wolak wrote: > On Wed, Feb 8, 2023 at 10:56 AM Kirk Wolak wrote: > >> On Wed, Feb 8, 2023 at 3:08 AM Pavel Stehule >> wrote: >> >>> hi >>> >>> st 8. 2. 2023 v 7:33 odesílatel Julien Rouhaud >>> napsal: >>> On Tue, Feb 07, 2023 at 08:48:22PM +0100, Pave

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-03-26 Thread Kirk Wolak
On Wed, Feb 8, 2023 at 10:56 AM Kirk Wolak wrote: > On Wed, Feb 8, 2023 at 3:08 AM Pavel Stehule > wrote: > >> hi >> >> st 8. 2. 2023 v 7:33 odesílatel Julien Rouhaud >> napsal: >> >>> On Tue, Feb 07, 2023 at 08:48:22PM +0100, Pavel Stehule wrote: >>> > >>> > GET DIAGNOSTICS _oid = PG_ROUTINE_O

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-02-08 Thread Kirk Wolak
On Wed, Feb 8, 2023 at 3:08 AM Pavel Stehule wrote: > hi > > st 8. 2. 2023 v 7:33 odesílatel Julien Rouhaud > napsal: > >> On Tue, Feb 07, 2023 at 08:48:22PM +0100, Pavel Stehule wrote: >> > >> > GET DIAGNOSTICS _oid = PG_ROUTINE_OID; >> > RAISE NOTICE '... % ... %', _oid, _oid::regproc::text; >

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-02-08 Thread Pavel Stehule
hi st 8. 2. 2023 v 7:33 odesílatel Julien Rouhaud napsal: > On Tue, Feb 07, 2023 at 08:48:22PM +0100, Pavel Stehule wrote: > > > > I have a question about the possibility of simply getting the name of the > > currently executed function. The reason for this request is > simplification > > of w

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-02-07 Thread Julien Rouhaud
On Tue, Feb 07, 2023 at 08:48:22PM +0100, Pavel Stehule wrote: > > I have a question about the possibility of simply getting the name of the > currently executed function. The reason for this request is simplification > of writing debug messages. > > GET DIAGNOSTICS _oid = PG_ROUTINE_OID; > RAISE N

Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-02-07 Thread Kirk Wolak
On Tue, Feb 7, 2023 at 2:49 PM Pavel Stehule wrote: > Hi > > I have a question about the possibility of simply getting the name of the > currently executed function. The reason for this request is simplification > of writing debug messages. > > GET DIAGNOSTICS _oid = PG_ROUTINE_OID; > RAISE NOTIC

possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID

2023-02-07 Thread Pavel Stehule
Hi I have a question about the possibility of simply getting the name of the currently executed function. The reason for this request is simplification of writing debug messages. GET DIAGNOSTICS _oid = PG_ROUTINE_OID; RAISE NOTICE '... % ... %', _oid, _oid::regproc::text; The advantage of this d