[BUGS] BUG #5698: pg_dump (8.3.11) does not consider constrains
The following bug has been logged online: Bug reference: 5698 Logged by: Johannes Meidert Email address: johannes.mei...@rohde-schwarz.com PostgreSQL version: 8.3.11, 9.0.1 Operating system: Windows Description:pg_dump (8.3.11) does not consider constrains Details: pg_dump dumps tables in the worng order for constraints (table a refrences key of table b, but table a is dumped first). As a consequence an import fails, because the required foreign key (in table b) is missing when table a is imported. Work around: import twice. Is this fixed in version 9.0? -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #5699: Postgres runs only under default user.
The following bug has been logged online: Bug reference: 5699 Logged by: Johannes Meidert Email address: johannes.meid...@rohde-schwarz.com PostgreSQL version: 9.0.1 Operating system: windows Description:Postgres runs only under default user. Details: If a --superaccount is specified during installation other than 'postgres', the service will not start correctly and there are lots of errors "role does not exist" in the DB error log. The option -- superaccount should be removed. Work around: use postgres and add the user later. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #5700: double-quoting column names
The following bug has been logged online:
Bug reference: 5700
Logged by: Piergiorgio Buongiovanni
Email address: piergiorgio.buongiova...@netspa.it
PostgreSQL version: 8.4.3
Operating system: Linux Redhat
Description:double-quoting column names
Details:
Dear all,
recently we experienced a strange behaviour with double quoting of column
names in UPDATE statements.
If you define a table as follows:
create table erc.TestTable ( Name varchar );
and then execute the following statement:
INSERT INTO erc.TestTable( "Name" ) VALUES ('Test');
you obtain the following error:
ERROR: column "Name" of relation "TestTable" does not exist
LINE 1: INSERT INTO erc.TestTable( "Name" ) VALUES ('Test');
If you try to execute the following statement instead of the previous one:
INSERT INTO erc.TestTable( "name" ) VALUES ('Test');
your SQL statement works well.
As you can see the difference is in the column name: "Name" versus "name".
Moreover if you try to execute the following statement:
INSERT INTO erc.TestTable( Name ) VALUES ('Test');
the query returns successfully and the row is inserted in the database.
As you can see the only difference between the first statement and the last
one is the use of "" to quote the column name.
Can you explain why the DB Engine has this behaviour if you use "" to quote
the column name? We always use the quote_indent function when we prepare a
SQL statement (string) for execution and this strange behaviour causes an
error when we execute the statement.
Regards
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5698: pg_dump (8.3.11) does not consider constrains
On Fri, Oct 08, 2010 at 11:46:31AM +, Johannes Meidert wrote: > pg_dump dumps tables in the worng order for constraints (table a refrences > key of table b, but table a is dumped first). As a consequence an import > fails, because the required foreign key (in table b) is missing when table a > is imported. > Work around: import twice. > Is this fixed in version 9.0? Could you give details of exactly what pg_dump commands you used? By default pg_dump dumps tables and data without any constraints first, and then adds constraints in a valid order. If, however, you do something like dump the schema first, and then dump data into that schema, there's little pg_dump can do to avoid problems such as you describe. -- Joshua Tolley / eggyknap End Point Corporation http://www.endpoint.com signature.asc Description: Digital signature
Re: [BUGS] BUG #5700: double-quoting column names
On Fri, Oct 08, 2010 at 12:20:35PM +, Piergiorgio Buongiovanni wrote:
> recently we experienced a strange behaviour with double quoting of column
> names in UPDATE statements.
>
> If you define a table as follows:
>
> create table erc.TestTable ( Name varchar );
>
> and then execute the following statement:
>
> INSERT INTO erc.TestTable( "Name" ) VALUES ('Test');
>
> you obtain the following error:
>
> ERROR: column "Name" of relation "TestTable" does not exist
> LINE 1: INSERT INTO erc.TestTable( "Name" ) VALUES ('Test');
The problem is you didn't double-quote the field name when you created the
table, so the column name was created in lowercase. From the documentation:
"Quoting an identifier also makes it case-sensitive, whereas unquoted names
are always folded to lower case." [1] So your CREATE TABLE statement created a
table called "erc.testtable" with a column called "name", and when you tried
to insert into a column called "Name", it failed.
I wonder, though, if you've shown us exactly what you did or not; in my
systems, the table name in the error message would all be lowercase. In any
event, as a rule, if you're going to quote your identifiers once, you need to
quote them all the time. For that reason, many people choose to stick with all
lowercase table and column names.
[1] http://www.postgresql.org/docs/9.0/interactive/sql-syntax-lexical.html
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
signature.asc
Description: Digital signature
[BUGS] bug report
what other information do you need from me to make this useful? configure: WARNING: uuid.h: present but cannot be compiled configure: WARNING: uuid.h: check for missing prerequisite headers? configure: WARNING: uuid.h: see the Autoconf documentation configure: WARNING: uuid.h: section "Present But Cannot Be Compiled" configure: WARNING: uuid.h: proceeding with the preprocessor's result configure: WARNING: uuid.h: in the future, the compiler will take precedence configure: WARNING: ## ## configure: WARNING: ## Report this to pgsql-bugs@postgresql.org ## configure: WARNING: ## ## -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
