Neil Conway <[EMAIL PROTECTED]> writes:
> Evidently the optimizer chooses a different plan in the presence of the
> WHERE clause, but that plan appears to be pretty bad. However, it is
> tough to say more without EXPLAIN output for both queries (if possible,
> get EXPLAIN ANALYZE output -- altho
Shujun Huang wrote:
RENCENTLY I RAN INTO THIS ERROR CODE 25P01 WHICH IS "NO ACTIVE SQL
TRNASACTION". THE POSTMASTER IS RUNNING OK. THIS HAPPENED AFTER WE UPGRADED
FROM 7.4.6 TO 7.4.7.
ANY INSERT/UPDATE QUERY RUNS OK, A SIMPLE RETRIEVE QUERY IS ALSO RUNNING OK,
ANY RETRIEVE QUERIES INVOLVE IN CURSO
Richard Sang wrote:
I have a view defined as :
create view calling_view as
(
select d.*,c.patient_id as id_m,c.result as r_m from
(select a.*,b.patient_id as id_f,b.result as r_f from
( select substr(a.family_id,1,4) as fid,b.* from denver_person a,
luminex b
where a.id=b.patient_id and
"Alexis Wilke" <[EMAIL PROTECTED]> writes:
> Operating system: Linux
You need to be a lot more specific than that, because this stuff works
fine on all the variants of Linux we know about.
> ERROR: Load of file /usr/local/pgsql/lib/ltree.so failed:
> /usr/local/pgsql/lib/ltree.so: undefined sy
"Alexis Wilke" <[EMAIL PROTECTED]> writes:
> Inside pgxs.mk I had to change the $$libdir into $(libdir ) to get the
> proper path in the final .sql file:
> ifneq (,$(MODULES)$(MODULE_big))
> %.sql: %.sql.in
> sed 's,MODULE_PATHNAME,$(libdir)/$*,g' $< >$@
> endif
This is not correct --- th
"Markus Bertheau" <[EMAIL PROTECTED]> writes:
> Description:RPM: wrong quoting of error message about old database
> format after upgrading
> [EMAIL PROTECTED] ~]$ sudo /etc/init.d/postgresql start
> An old version of the database format was found.\nYou need to upgrade the
> data format b
Title: Message
Yes,
those are not related at all to the actual error.
Can
you zip up the full log and send it to me off-list? It's still missing the
important part :-) Either that, or windows installer isn't telling us the
important part...
//Magnus
-Original Message-From:
>The following bug has been logged online:
>
>Bug reference: 1488
>Logged by: Jesper Udby
>Email address: [EMAIL PROTECTED]
>PostgreSQL version: 8.0.1
>Operating system: Win32 XP Pro SP2
>Description:CREATE TABLESPACE does not work
>Details:
>
>Hello.
>
>Trying to crea
Jesper Udby wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1488
> Logged by: Jesper Udby
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.1
> Operating system: Win32 XP Pro SP2
> Description:CREATE TABLESPACE does not work
> Detail
Tom M. Yeh wrote:
Yes, it really depends on Locale. If I created a
database with Locale = C, the problem won't happen (at
least so far). BTW, I forgot to mention I tested with
some Chinese and Japanese characters.
However, it raises another issue why a wrong Locale
would damage index? It shall only
> -Original Message-
> From: Richard Huxton [mailto:[EMAIL PROTECTED]
> Sent: 21 February 2005 16:13
> To: Dave Page
> Cc: Tom Yeh; pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #1487: Index problem
>
> > pgAdmin uses libpq, just as psql does, so I cannot imagine why this
> > wou
Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard Huxton
Sent: 21 February 2005 15:37
To: Tom Yeh
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #1487: Index problem
The above can be replicated by using pgAdmin III only.
Ar
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Richard Huxton
> Sent: 21 February 2005 15:37
> To: Tom Yeh
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #1487: Index problem
>
> > The above can be replicated by using pgAdmin III only
Tom Yeh wrote:
I created an index for a table, say Entity, on a field, say id.
Then, the follwoing two SQL has different result:
select * from "Entity" e where e.id = '1000'
select * from "Entity" e where e.id like '1000'
What is the definition of "Entity"?
How many rows are there in the table?
Ho
The following bug has been logged online:
Bug reference: 1495
Logged by: Markus Bertheau
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Fedora Core 3
Description:RPM: wrong quoting of error message about old database
format after upgradin
Hannes Erven wrote:
The following bug has been logged online:
Bug reference: 1485
Logged by: Hannes Erven
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: 2.6.10-gentoo-r6
Description:upper case user names / creatuser
Details:
template1=# a
Andrew Gold wrote:
The following bug has been logged online:
Bug reference: 1486
Logged by: Andrew Gold
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: Debian Linux
Description:Apostrophes are not ignored in pgplsql comments
Details:
In pg
You need to look a bit earlier in the logfile to
determine where the error is - the log you have here is only from the MSI
rollback.
How far into the installation do you get befoer it
fails?
//Magnus
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
JuuSent: Su
18 matches
Mail list logo
