Hi Tom,
Tom Lane wrote:
The first of these looks like the same problem we've seen reported
before of a table's rowtype not getting dropped when the table is
dropped.
I'm a newbie with PG and i do not understand the meaning of "a table's rowtype
not getting dropped when the table is
dropped."
Jens Wendelmuth <[EMAIL PROTECTED]> writes:
> I'm a newbie with PG and i do not understand the meaning of "a table's
> rowtype not getting dropped when the table is
> dropped."
Every table has an associated composite type of the same name, which
represents the type of each row of the table. This
Alexander Presber <[EMAIL PROTECTED]> writes:
> We encounter the following two strange errormessages when working
> with temporary tables.
> 1) ERROR: duplicate key violates unique constraint
> "pg_type_typname_nsp_index"
> 2) ERROR: tuple concurrently updated
The first of these looks like
Hello everyone,
We encounter the following two strange errormessages when working
with temporary tables.
1) ERROR: duplicate key violates unique constraint
"pg_type_typname_nsp_index"
2) ERROR: tuple concurrently updated
This is how:
To cache large resultsets of searches we select them
