On fre, 2009-11-06 at 17:29 +, Jason wrote:
When I have a plpythonu function returning a composite type that has an
array column, the function does not work when I try to return a list for
that column.
There is a patch proposed to address that in 8.5, but before that,
arrays are pretty
The following bug has been logged online:
Bug reference: 5174
Logged by: Richard Neill
Email address: rn...@cam.ac.uk
PostgreSQL version: 8.4.1
Operating system: Linux
Description:[minor] directories symlinked into base/ are not
recursively removed
Details:
This is
Hello,
I hope it's not a bug, but I get an exclusive lock in a CREATE TABLE AS
SELECT statement, contained in the following function/transaction:
-- this is an alternative to CLUSTER TABLE, you know, create a
-- sorted clone of the table,then create all indexes, FKs and
-- then switch to new
On Sat, Nov 7, 2009 at 5:23 AM, Peter Eisentraut pete...@gmx.net wrote:
On fre, 2009-11-06 at 17:29 +, Jason wrote:
When I have a plpythonu function returning a composite type that has an
array column, the function does not work when I try to return a list for
that column.
There is a
Hello,
I hope it's not a bug, but I get a deadlock error in a
function/transaction with these statements:
CREATE OR REPLACE FUNCTION cluster_adc_table () RETURNS INTEGER AS $$
BEGIN
DROP TABLE IF EXISTS adc_clustered;
RAISE NOTICE 'start creating clustered table at %s',
The following bug has been logged online:
Bug reference: 5172
Logged by: Viisard
Email address: viis...@hotmail.com
PostgreSQL version: 8.4.1
Operating system: Fedora 11 (Linux 2.6.30.9-96.fc11.i686.PAE)
Description:ecpg - cursor with regexp containing '.*/' fails to
digital.de...@gmx.it digital.de...@gmx.it writes:
I hope it's not a bug, but I get a deadlock error in a
function/transaction with these statements:
It's not a bug. The CREATE TABLE AS SELECT is acquiring a read lock on
table adc, and then the ALTER TABLE RENAME tries to upgrade that lock
to
Richard Neill rn...@cam.ac.uk writes:
If subdirectories of base/ are actually symlinks, then postgresql deletes
just the symlink, not the directory.
Doing that is completely unsupported, and we cannot be expected to cope
with random manual modifications to the structure of the database. Why
Tom Lane wrote:
Richard Neill rn...@cam.ac.uk writes:
If subdirectories of base/ are actually symlinks, then postgresql deletes
just the symlink, not the directory.
Doing that is completely unsupported, and we cannot be expected to cope
with random manual modifications to the structure of
It's your fault though I don't know how you would know that without
knowing a lot about how postgres handles internal locking.
The problem is that the creat table as select * from adc takes a share
lock on adc then later the rename table upgrades the lock. This is
always a deadlock risk.
10 matches
Mail list logo
