From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
---|---|
To: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | PL/R Median Busts Commit (Postgres 9.1.6 + plr 8.3.0.13 on Ubuntu 12.10 64 bit) |
Date: | 2013-01-24 04:21:06 |
Message-ID: | 5100B6B2.8030408@catalyst.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I admit - it sounds unlikely. However a simple scenario (attached) gives
rise to:
WARNING: AbortTransaction while in COMMIT state
PANIC: cannot abort transaction 880983, it was already committed
Essentially we are doing:
BEGIN;
DROP TABLE IF EXISTS tab0;
CREATE TEMP TABLE tab0 ( id INTEGER PRIMARY KEY, val TEXT);
INSERT INTO tab0 SELECT generate_series(1,1000),'xxxxxxxxxx';
SELECT median(id) FROM tab0;
DROP TABLE IF EXISTS tab1;
CREATE TEMP TABLE tab1 ( id INTEGER PRIMARY KEY, val TEXT);
INSERT INTO tab1 SELECT generate_series(1,1000),'xxxxxxxxxx';
DROP TABLE IF EXISTS tab2;
...
DROP TABLE IF EXISTS tab99;
CREATE TEMP TABLE tab99 ( id INTEGER PRIMARY KEY, val TEXT);
INSERT INTO tab99 SELECT generate_series(1,1000),'xxxxxxxxxx';
SELECT median(id) FROM tab99;
COMMIT;
We crash at commit.
Changing median to something else (e.g avg or even a non PLR median
function) makes the error vanish, so its either PLR or the specific PLR
median function causing the grief.
Regards
Mark
Attachment | Content-Type | Size |
---|---|---|
median.sql | text/x-sql | 217 bytes |
temp.sql | text/x-sql | 15.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ben Morgan | 2013-01-24 06:32:59 | Re: psql \d command hides objects from "lower" schemas |
Previous Message | Georgi Georgiev | 2013-01-24 03:55:31 | Re: BUG #7823: PGDG packaged pgadmin3_92 removes its /usr/bin/pgadmin3 link |