|
Home > Archive > PostgreSQL Discussion > May 2005 > Re: CREATE TEMP TABLE AS SELECT/ GET DIAGNOSTICS ROW_COUNT
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: CREATE TEMP TABLE AS SELECT/ GET DIAGNOSTICS ROW_COUNT
|
|
| Bruce Momjian 2005-05-30, 8:23 pm |
|
Can someone in the community comment on this question? I don't know the
answer.
---------------------------------------------------------------------------
MLikharev@micropat.com wrote:
> Hi, I was asking this question some time ago and was under impression
> that this will be fixed in 8.x. In general problem is, CREATE TEMP
> TABLE AS SELECT does not report any rows to the engine, seems like, so
> GET DIAGNOSTICS ROW_COUNT after the statement returns 0 as well as
> FOUND false. This was working in 7.3, but behavior changed in 7.4. My
> question is, will it be fixed or should I consider not stop using get
> diagnostic after ?create temp table as select? from now on. Honstly
> this was a very convinient feature especialy knowing that select
> count(*) not a fastes possible operation.
>
> Thank you.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql
.org so that your
> message can get through to the mailing list cleanly
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
| |
| Tom Lane 2005-05-30, 8:23 pm |
| Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Can someone in the community comment on this question? I don't know the
> answer.
I think it could be changed back without much work, but I have a feeling
that we'd deliberately decided on the change of behavior. Can anyone
recall a prior discussion, or want to vote with or against MLikharev?
Note that the change is actually at the SPI level, and would affect
SPI_processed for all code using CREATE AS/SELECT INTO through SPI,
not only plpgsql.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
|
|
|
|
|