On Fri, 8 Aug 2003, Tom Lane wrote:
Stephan Szabo [EMAIL PROTECTED] writes:
I got the same thing as Gaetano on my just prior to beta1 system.
Well, we couldn't have fixed it since beta1 --- there's been no changes
anywhere near SPI. I'm thinking it must be platform-dependent. What
are
I forgot to say to do a:
select bar()
at the end!
Gaetano
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Fri, 2003-08-08 at 11:55, Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
the following code was working properly under Postgres 7.3.X
I'm now running my regression test with Postgres 7.4beta1 and I'm
having the error in subj.
I tried this and got
regression=# select
Stephan Szabo [EMAIL PROTECTED] writes:
I got the same thing as Gaetano on my just prior to beta1 system.
Well, we couldn't have fixed it since beta1 --- there's been no changes
anywhere near SPI. I'm thinking it must be platform-dependent. What
are you guys using, exactly?
Mendola Gaetano [EMAIL PROTECTED] writes:
Again the error:
kalman=# select bar();
ERROR: consistency check on SPI tuple count failed
CONTEXT: PL/pgSQL function bar line 5 at for over select rows
kalman=# select bar();
ERROR: consistency check on SPI tuple count failed
CONTEXT: PL/pgSQL
Hi all,
the following code was working properly under Postgres 7.3.X
I'm now running my regression test with Postgres 7.4beta1 and I'm
having the error in subj.
CREATE TABLE test ( a integer, b integer );
INSERT INTO test VALUES ( 1 );
CREATE OR REPLACE FUNCTION foo(INTEGER)
RETURNS INTEGER AS'
Tom Lane [EMAIL PROTECTED] wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
the following code was working properly under Postgres 7.3.X
I'm now running my regression test with Postgres 7.4beta1 and I'm
having the error in subj.
I tried this and got
regression=# select bar();
bar
Mendola Gaetano [EMAIL PROTECTED] writes:
Incredible to believe but after playng around that funcion started
to work. I'm not crazy.
Yeah, it was a problem with storing into a possibly-obsolete pointer ---
the visible effects could range from nothing to a core dump depending on
whether the
Gaetano Mendola [EMAIL PROTECTED] writes:
the following code was working properly under Postgres 7.3.X
I'm now running my regression test with Postgres 7.4beta1 and I'm
having the error in subj.
I tried this and got
regression=# select bar();
bar
-
0
(1 row)
regression=#
Anyone else
Tom Lane [EMAIL PROTECTED]
Stephan Szabo [EMAIL PROTECTED] writes:
I got the same thing as Gaetano on my just prior to beta1 system.
Well, we couldn't have fixed it since beta1 --- there's been no changes
anywhere near SPI. I'm thinking it must be platform-dependent. What
are you guys
On Fri, 8 Aug 2003, Tom Lane wrote:
Mendola Gaetano [EMAIL PROTECTED] writes:
Again the error:
kalman=# select bar();
ERROR: consistency check on SPI tuple count failed
CONTEXT: PL/pgSQL function bar line 5 at for over select rows
kalman=# select bar();
ERROR: consistency check
Stephan Szabo [EMAIL PROTECTED] writes:
On Fri, 8 Aug 2003, Tom Lane wrote:
I have also just traced through _SPI_cursor_operation() in spi.c,
watched PortalRunFetch return 2, and then watched _SPI_checktuples read
zero from _SPI_current-processed. How the heck could that happen?
Compiler
On Fri, 8 Aug 2003, Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
the following code was working properly under Postgres 7.3.X
I'm now running my regression test with Postgres 7.4beta1 and I'm
having the error in subj.
I tried this and got
regression=# select bar();
bar
13 matches
Mail list logo
