[EMAIL PROTECTED] wrote:
> Chester Chee ([EMAIL PROTECTED]) reports a bug with a severity
> of 2 The lower the number the more severe it is.
>
> Short Description Old bug is back!! Drop database bug
>
> Long Description PostgreSQL version 7.2.1 running on RedHat 7.3 with
> all the latest pa
Jie Liang <[EMAIL PROTECTED]> writes:
> I use:
> pg_dump -Fc -d urldb > urldb.out.020810
^^
There you have it. Better read the pg_dump help output again.
regards, tom lane
---(end of broadcast)---
TIP 4: Don'
Jie Liang <[EMAIL PROTECTED]> writes:
> pg_restore give admin a lot of flexabilities, it can restore any object
> from a single dump file. But if the table is very big, e.g. 2M records,
> it will take a long time to restore because it use INSERTs.
This is demonstrably not the case --- at least no
Chester Chee ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Old bug is back!! Drop database bug
Long Description
PostgreSQL version 7.2.1 running on RedHat 7.3 with all the latest patches installed.
Step to reproduce the prob
[EMAIL PROTECTED] writes:
> Following is the example of sql script that crashes server if you
> remove marked comments (this is not real code, just test one).
> May be i am doing something wrong???
Changing the trigger set on a relation from within a trigger on that
same relation is not a good pl
Konstantin Katuev ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Server crash when using dynamic SQL and disabling recursion
Long Description
When trying to develop trigger on plpgsql, that will update the own relation,
i met
