[BUGS] BUG #4295: DELETE WHERE Condition
The following bug has been logged online: Bug reference: 4295 Logged by: Fred Perniss Email address: [EMAIL PROTECTED] PostgreSQL version: all Versions Operating system: Open SuSe Linux 11 Description:DELETE WHERE Condition Details: Fist: Sorry for my bad english. I have 2 tables table t1 with fields t1.t1_id, t1.t1_value table t2 with fields t2.t2_id, t2.t2_t1_id, t2.t2_value table t2 have a forign key to table t1 (t2_t1_id) I have to delete all rows from table t2 with the condition t1.t1_value = 5. In Postgres the switch add_mising_from=on the SQL-Command DELETE FROM t2 WHERE (t2.t2_t1_id=t1.t1_id) AND t1.t1_inhalt=5 ; works (with message in Log). If the switch add_missing_from=off following Error-Message will be promted: Fehlender Eintrag in FROM Klausel für Tabelle t1 The new Syntax from SQL in MySQL Version 4 DELETE FROM T2 FROM t1, t2 WHERE (t2.t2_t1_id=t1.t1_id) AND t1.t1_inhalt=5 ; is not implemented. I don't find any other Syntax for this and I don't find any in the log, how I can change the sytax or how postgre do this if the switch add_mising_from is on. Can you tell me the correct syntax or can you tell me how the server transform the query if the switch is set to on? -- 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 #4295: DELETE WHERE Condition
Am Freitag, 11. Juli 2008 schrieb Fred Perniss: > In Postgres the switch add_mising_from=on the SQL-Command > > DELETE FROM t2 > WHERE (t2.t2_t1_id=t1.t1_id) > AND t1.t1_inhalt=5 > ; > > works (with message in Log). > > If the switch add_missing_from=off following Error-Message will be promted: > > Fehlender Eintrag in FROM Klausel für Tabelle t1 You want to use DELETE .. USING. See the man page for details. -- 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 #4296: Server crashes by restoring database
The following bug has been logged online: Bug reference: 4296 Logged by: Michal Szelag Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3.3 Operating system: 2.6.23-1-amd64[debian etch] Description:Server crashes by restoring database Details: Hallo, very sory for my bad english: i have a server crash by retoring database. I try to retore my database from a custom package with pg_restore and prom a plain package with psql. In both i have the same problem, psl and pg_restore outputs: pg_restore: [archiver (db)] error returned by PQputCopyData: server closed the connection unexpectedly and i have messages in my log file: server process (PID 11351) exited with exit code 255 terminating any other active server processes all server processes terminated; reinitializing my database contains composite types and array composite types. Can you tell me, haw can i restore my database? Best Regerds, M.Sz. -- 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 #4291: Inheritance fails on column suppression
Thank you very much for your answer. In the documentation, the last lines of chapter 5.8 say : " A parent table cannot be dropped while any of its children remain. Neither can columns of child tables be dropped or altered if they are inherited from any parent tables. If you wish to remove a table and all of its descendants, one easy way is to drop the parent table with the CASCADE option. ALTER TABLE will propagate any changes in column data definitions and check constraints down the inheritance hierarchy. Again, dropping columns or constraints on parent tables is only possible when using the CASCADE option. ALTER TABLE follows the same rules for duplicate column merging and rejection that apply during CREATE TABLE." Reading this, I understand that using the CASCADE key word in the alter synthax means that the child columns will be dropped too. Especially reading the paragraph just before this one, which says : "Table inheritance is typically established when the child table is created, using the INHERITS clause of the CREATE TABLE statement. Alternatively, a table which is already defined in a compatible way can have a new parent relationship added, using the INHERIT variant of ALTER TABLE. To do this the new child table must already include columns with the same names and types as the columns of the parent. It must also include check constraints with the same names and check expressions as those of the parent. Similarly an inheritance link can be removed from a child using the NO INHERIT variant of ALTER TABLE. Dynamically adding and removing inheritance links like this can be useful when the inheritance relationship is being used for table partitioning (see Section 5.9). " Regards, C. Duprez -- Initial Header --- From : Tom Lane <[EMAIL PROTECTED]> To : "Duprez" <[EMAIL PROTECTED]> Cc : pgsql-bugs@postgresql.org Date : Thu, 10 Jul 2008 10:34:19 -0400 Subject : Re: [BUGS] BUG #4291: Inheritance fails on column suppression "Duprez" <[EMAIL PROTECTED]> writes: > Then, I remove th inheritance link by performing an ALTER command : > ALTER TABLE test2.point NO INHERIT test1.point; > And then, I restablish the inheritance : > ALTER TABLE test2.point INHERIT test1.point; > The problem is that, if now I drop a column from the parent table, the > column remains in the child table, whereas the inheritance is established : This is not a bug. Once the child was dis-inherited, all its columns became locally defined, and they'd stay that way on re-inheritance. (There is no memory in the system that would allow us to determine that the attislocal flag should be removed --- that is, we can't tell this case from the case where column test2 was declared locally in the original child table definition. It doesn't seem worth adding still more complexity to the column inheritance state just to cover this.) > According to the documentation, this should not be the case. Please state where you think the documentation says that, so we can fix it. regards, tom lane -- ALICE N°1 de la RELATION CLIENT 2008* Découvrez vite l'offre exclusive ALICE BOX! En cliquant ici http://abonnement.aliceadsl.fr Offre soumise à conditions.*Source : TNS SOFRES / BEARING POINT. Secteur Fournisseur d.Accès Internet -- 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 #4296: Server crashes by restoring database
"Michal Szelag" <[EMAIL PROTECTED]> writes: > i have a server crash by retoring database. > I try to retore my database from a custom package with pg_restore and prom a > plain package with psql. In both i have the same problem, psl and pg_restore > outputs: > pg_restore: [archiver (db)] error returned by PQputCopyData: server closed > the connection unexpectedly You're evidently tripping over some kind of bug, but we can't help you without a lot more detail than this. Try to identify the exact command that's crashing (hint: turn on log_statements and watch the postmaster log). See if you can put together a self-contained script that causes the crash. That will let us fix the problem, and it might let you find a workaround to reload your data even in advance of a real fix. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] Olá
Olá, preciso instalar o postgres 8.1.4 no windows server 2008 com active directory instalado, pode me ajudar ? Não estou conseguindo instalar, dá erro, acho que é por causa do AD. Atenciosamente, Marcos Fabrício Corso Analista de Sistemas Júnior JM Informática Fone : (41) 3076-0896 Fax : (41) 3352-2688 [EMAIL PROTECTED] www.informaticajm.com.br
