: pgsql-bugs@postgresql.org
Cc: Mikael Carneholm
Subject: Re: [BUGS] unterminated dollar-quoted string at or near "$$
language plpgsql;" at character 1
Mikael Carneholm wrote:
> This seems to be a psql(?) bug:
It seems you're using an older version of psql.
--
Pet
This seems to be a psql(?) bug:
test.sql
create or replace function test1() returns void as $$
declare
var1 integer;
var2 integer;
var3 integer;
begin
end;
$$ language plpgsql;
miano=> \i test.sql
psql:test.sql:3: ERROR: unterminated dollar-quoted string at or near "$$
declar
27;m pretty sure though that 15865 was the autovacuum process, but I'll have to
run the function with autovacuum turned on before I can verify that this is
(was) the case.
/Mikael
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: den 17 november 2005 17:42
To:
022.
So it seems that it was the clustering of
idx_vehicle_unit_data_200407_person_information__id on vehicle_unit_data_200407
that caused the deadlock.
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: den 17 november 2005 16:53
To: Mikael Carneholm
Cc: pg
gone)
Could it be that the deadlock was caused by autovacuum trying to vacuum one of
the temp copies?
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: den 17 november 2005 16:04
To: Mikael Carneholm
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Autovacuum deadlock - bug o
AIL PROTECTED]
Sent: den 17 november 2005 16:04
To: Mikael Carneholm
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Autovacuum deadlock - bug or not?
"Mikael Carneholm" <[EMAIL PROTECTED]> writes:
> variant: CLUSTER indexname ON tablename
Hmph. Looking at the code, that
: den 17 november 2005 15:51
To: Mikael Carneholm
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Autovacuum deadlock - bug or not?
"Mikael Carneholm" <[EMAIL PROTECTED]> writes:
> Don't know if this is a bug or just undocumented, but it seems as you should
> tu
Don't know if this is a bug or just undocumented, but it seems as you should
turn off autovacuum before you run CLUSTER, otherwise you might run into a
deadlock:
NOTICE: Clustering idx_vehicle_unit_data_200407_person_information__id on
vehicle_unit_data_200407
ERROR: deadlock detected
DETAIL:
tecol
mastertab_feb05|2|2005-02-01
(row with id 1 was deleted but not re-inserted)
/Mikael
-Original Message-
From: Mikael Carneholm
Sent: den 5 november 2005 23:05
To: 'pgsql-bugs@postgresql.org'
Subject: create OR REPLACE rule bug
I believe
I believe this is a bug:
-- OR REPLACE present
create or replace rule "mastertab_jan05_update" as
on update to mastertab where
(NEW.datecol < '20050101' or NEW.datecol >= '20050201')
and
(OLD.datecol >= '20050101' and OLD.datecol < '20050201')
do instead (
-- multiple commands
delet
10 matches
Mail list logo
