"Casey Duncan" <[EMAIL PROTECTED]> writes:
> CREATE FUNCTION write_error_trigf() RETURNS trigger AS '
> BEGIN
> RAISE EXCEPTION ''Writes not allowed to this table on this node'';
> END;
> ' LANGUAGE plpgsql;
> END; --Upgrade script
You did not show how this function is being used,
Hi Tom,
Tom Lane wrote:
>> Explain command does not report the schema of objects,
>
> This is intentional. Most error messages don't mention objects' schemas
> either, as it would usually just be clutter.
Oracle's EXPLAIN PLAN generate lots of information including the operation,
search columns,
"Cristiano da Cunha Duarte" <[EMAIL PROTECTED]> writes:
> Explain command does not report the schema of objects,
This is intentional. Most error messages don't mention objects' schemas
either, as it would usually just be clutter.
regards, tom lane
---
"Andy" <[EMAIL PROTECTED]> writes:
> To try and reproduce the problem on another machine, I did a new install of
> the same version of Postgres (8.1.3) and dump/restored the database onto
> this new server. So far it has been running with the same load and activity
> for almost 30 hours and the pr
The following bug has been logged online:
Bug reference: 2429
Logged by: Cristiano da Cunha Duarte
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Debian GNU Linux
Description:Explain does not report object's schema
Details:
1) PROBLEM:
E
Hi,
Thank
you for your replies.
I
accept that the "Permission denied" problem does suggest that the DB
error may be caused by the OS somehow.
There
is no problem with the permissions/ownership of the files because the Postgres
account created and owns and those files; this rul
The following bug has been logged online:
Bug reference: 2426
Logged by: Chana Slutzkin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: FreeBSD 6.1
Description:perl function that returns setof composite type
Details:
The code below works
The following bug has been logged online:
Bug reference: 2428
Logged by: Casey Duncan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Debian Linux (2.6.13.1-20050914 #2 SMP) 2xOpteron 8GB
RAM
Description:ERROR: out of memory, running INSE
On Mon, 2006-05-08 at 08:31 -0400, Alvaro Herrera wrote:
> > 2006-05-07 23:44:20 10.10.12.100(4018)PANIC: 42501: could not write to log
> > file 0, segment 90 at offset 2998272, length 8192: Permission denied
This is a pg_xlog error, so it looks like you have a whole-system issue,
not just isolat
