Oh, there's another solution I forgot to mention: you could write the
nextval call as
nextval('s'::text)
which would force a runtime lookup of 's' on each call. On the whole
though, numbering the rows yourself with a local counter is going to
run a lot faster.
rega
"Robins Tharakan" <[EMAIL PROTECTED]> writes:
> BEGIN
> CREATE TEMPORARY SEQUENCE s INCREMENT BY 1 START WITH 1;
> FOR rec in
> SELECT nextval('s') as rank, tt.scheme_code, tt.ret
> ...
> DROP SEQUENCE s;
> END;
Sorry, that's not going to work, for fundamentally the same re
What if the new query has a significantly lower cost compared to the older
one?
The current query found in pgaJob.cpp:
SELECT *,
(SELECT jlgstatus FROM pgagent.pga_joblog jl WHERE jl.jlgjobid =
j.jobid ORDER BY jlgid DESC LIMIT 1) AS joblastresult
FROM pgagent.pga_job j
"Eric Weimer" <[EMAIL PROTECTED]> writes:
> Creating a table with a column of type serial causes the creation of a
> sequence tied as the default value for the column.
> The actual type of the column is integer, however the sequence created is of
> type bigint. If the sequence is created as a bigin
"Roberts, Jon" <[EMAIL PROTECTED]> writes:
> What if the new query has a significantly lower cost compared to the older
> one?
Much as I'd like the planner to be infallible, it ain't; estimated costs
are no proof of any real-world performance difference. Better show
EXPLAIN ANALYZE numbers if you
The following bug has been logged online:
Bug reference: 3668
Logged by: Eric Weimer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Linux
Description:type error in serial
Details:
Creating a table with a column of type serial causes the c
"Jon Roberts" <[EMAIL PROTECTED]> writes:
> Greenplum doesn't support "correlated subqueries" which PGAdmin III uses
> when PgAgent is installed.
Surely this complaint should be directed to Greenplum. Correlated
subqueries are a required entry-level feature in the SQL92 standard,
and have been
The following bug has been logged online:
Bug reference: 3667
Logged by: Jon Roberts
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Solaris
Description:Job scheduling with Greenplum fails
Details:
Greenplum doesn't support "correlated sub
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Adam PAPAI <[EMAIL PROTECTED]> writes:
>> Usually our program dumps core several times a day, but the reason is
>> unknown. All I know from the core file is the lines below.
>
> That failure is inside malloc, not PQmakeEmptyPQresult, and the odds
> are ext
"Evgeni" <[EMAIL PROTECTED]> writes:
> On SPI_exec see erorr ERROR: INSERT is not allowed in a non-volatile
> function
You didn't show us your code, but somehow or other you're managing to
pass read_only = true to the SPI execution code.
regards, tom lane
--
The following bug has been logged online:
Bug reference: 3666
Logged by: Yves
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: LInux
Description:Truncated Parameter in LDAP string when spaces contained
Details:
Hello,
It is not possible t
The following bug has been logged online:
Bug reference: 3665
Logged by: Evgeni
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.7
Operating system: Linux Redhat 7.2
Description:INSERT is not allowed in a non-volatile function
Details:
I write function in c
"Adam PAPAI" <[EMAIL PROTECTED]> writes:
> PostgreSQL version: (PostgreSQL) 7.4.7
Incidentally there have been 11 bug-fix releases to 7.4 since this one.
Several of those cause crashes or data corruption and you would be
well-advised to install 7.4.18 asap. Normally you don't need a dump/resto
Adam PAPAI <[EMAIL PROTECTED]> writes:
> Usually our program dumps core several times a day, but the reason is
> unknown. All I know from the core file is the lines below.
That failure is inside malloc, not PQmakeEmptyPQresult, and the odds
are extremely high that the reason is some part of your
Adam PAPAI
wooh (at) wooh (dot) hu
System Configuration
-
Architecture: Intel(R) Xeon(TM) CPU 2.80GHz
Operating System: Debian/GNU Linux i686 GNU/Linux
PostgreSQL version: (PostgreSQL) 7.4.7
Compiler used: gcc 3.3.6
Problem description
-
Usua
Euler Taveira de Oliveira wrote:
> Martin Pitt wrote:
> > For example, "psql -l" is a convenient
> > method to check whether the postmaster is running at all,
> > finished with startup and ready for connections.
>
> Why not just "pg_ctl status"?
That doesn't check whether the server is actually an
16 matches
Mail list logo
