Re: [BUGS] BUG #1118: Misleading Commit message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: elein <elein(at)varlena(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #1118: Misleading Commit message
Date: 2004-07-10 19:42:15
Message-ID: 19720.1089488535@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> MOVE, FETCH, EXECUTE ...

> Ah, yes, I remember we changed EXECUTE recently to return the tag of
> what we executed. How do we modify MOVE/FETCH tags? I can't remember.

I was just looking to see what cases ProcessUtility allowed to change
the tag. I think that what the code does is just to append the row
count, which you could argue isn't "changing the tag". But really,
is returning "UPDATE 0" vs "UPDATE 1" any different conceptually from
what we are talking about here? It's still using the tag to pass back
info about what the command actually did.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2004-07-10 19:42:55 Re: Nested Transactions, Abort All
Previous Message Bruce Momjian 2004-07-10 19:36:19 Re: [BUGS] BUG #1118: Misleading Commit message