[BUGS] BUG #3731: ash table "PROCLOCK hash" corrupted

The following bug has been logged online: Bug reference: 3731 Logged by: Daniel Cristian Cruz Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.4 Operating system: Red Hat ES 4 Description:ash table "PROCLOCK hash" corrupted Details: A few moments

Re: [BUGS] BUG #3731: ash table "PROCLOCK hash" corrupted

Em Qui, 2007-11-08 às 12:29 -0500, Tom Lane escreveu: > "Daniel Cristian Cruz" <[EMAIL PROTECTED]> writes: > > A few moments ago I got the following message, but didn't found any > > reference on the internet (including lists). > > > Nov 8 13:50

[BUGS] BUG #4037: Manual bug: 2.5. Querying a Table

The following bug has been logged online: Bug reference: 4037 Logged by: Daniel Cristian Cruz Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3 Operating system: Windows Description:Manual bug: 2.5. Querying a Table Details: Where it says: "Notice ho

Re: [BUGS] BUG #4037: Manual bug: 2.5. Querying a Table

Humm... Reading this way... It sounds like I could write something like this: SELECT city, (temp_hi+temp_lo)/2 temp_avg, date FROM weather; Like it work with tables... 2008/3/14, Tom Lane <[EMAIL PROTECTED]>: > > "Daniel Cristian Cruz" <[EMAIL PROTECTED]&g

[BUGS] Deferred Referential Constraint: Changing Referenced Key

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I was wondering if it is a bug or a feature. When I change a key on a referenced table, and there is a foreign key deferred constraint, it triggers imediately, not at the end of transaction. If I change the reference first, it works as expe

[BUGS] BUG #1740: Deferred foreign key constraint isn't deferred

The following bug has been logged online: Bug reference: 1740 Logged by: Daniel Cristian Cruz Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: Windows XP Professional Description:Deferred foreign key constraint isn't deferred De

Re: [BUGS] BUG #1740: Deferred foreign key constraint isn't deferred

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Big, big mistake... Thanks for the help, sorry about the post... Michael Fuhr wrote: > On Thu, Jun 30, 2005 at 02:01:39PM +0100, Daniel Cristian Cruz wrote: > >>ALTER TABLE ONLY mat_comissao_itens >>

[BUGS] BUG #6050: Dump and restore of view after a schema change: can't restore the view

The following bug has been logged online: Bug reference: 6050 Logged by: Daniel Cristian Cruz Email address: danielcrist...@gmail.com PostgreSQL version: 9.0.4 Operating system: Linux Description:Dump and restore of view after a schema change: can't restore the

Re: [BUGS] BUG #6050: Dump and restore of view after a schema change: can't restore the view

s not recommended since a schema change would crash backups. 2011/6/3 Tom Lane > "Daniel Cristian Cruz" writes: > > CREATE TABLE a ( > > id_a serial primary key, > > v text > > ); > > CREATE TABLE b ( > > id_b serial primary key, > > id_

Re: [BUGS] BUG #6050: Dump and restore of view after a schema change: can't restore the view

e not terribly > high on your priority list, I can understand that. But if you're > actually defending the current implementation, I'm going to have to > respectfully disagree. It's broken, and it sucks, and this is not the > first complaint we've had about it. > > -- > Robert Haas > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > -- Daniel Cristian Cruz クルズ クリスチアン ダニエル

[BUGS] ISBN: dump from 64bits and restore on 32 bits fail, Datum?

;t shows up. Naive I was trying to force Datum size to 8 and recompile postgresql for the 32 bits server. It doesn't work this way. :) Now I request some help from some PostgreSQL Olympian Gods... :) Regards, -- Daniel Cristian Cruz クルズ クリスチアン ダニエル

[BUGS] BUG #6225: Child table with a missing parent key which no exists in a complex trigger/cascade schema

The following bug has been logged online: Bug reference: 6225 Logged by: Daniel Cristian Cruz Email address: danielcrist...@gmail.com PostgreSQL version: 9.1.0 Operating system: "PostgreSQL 9.1.0 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2 20080704 (Re

[BUGS] BUG #6226: Broken foreign key stored on database (parent deleted with children still readable, BUG#6225 Update)

The following bug has been logged online: Bug reference: 6226 Logged by: Daniel Cristian Cruz Email address: danielcrist...@gmail.com PostgreSQL version: 9.1.1 Operating system: "PostgreSQL 9.1.0 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2 20080704 (Re

Re: [BUGS] BUG #6226: Broken foreign key stored on database (parent deleted with children still readable, BUG#6225 Update)

w setting null. But the thread is almost a book, and I am confused. It's a bug or do I need to change my schema? Where can I change it to avoid it? -- Daniel Cristian Cruz クルズ クリスチアン ダニエル

Re: [BUGS] BUG #6226: Broken foreign key stored on database (parent deleted with children still readable, BUG#6225 Update)

nced_id, repetition_conf.id_repetition_conf AS reference FROM repetition LEFT JOIN repetition_conf ON repetition.id_repetition_conf = repetition_conf.id_repetition_conf WHERE repetition_conf.id_repetition_conf IS NULL; -- Daniel Cristian Cruz クルズ クリスチアン ダニエル

Re: [BUGS] BUG #6226: Broken foreign key stored on database (parent deleted with children still readable, BUG#6225 Update)

have to be saved until end of statement." I became a rusty DBA poluting pgsql-bugs, sorry. RTFM for myself. :) -- Daniel Cristian Cruz クルズ クリスチアン ダニエル

Re: [BUGS] BUG #6226: Broken foreign key stored on database (parent deleted with children still readable, BUG#6225 Update)

Changing BEFORE DELETE to AFTER DELETE worked. 2011/10/5 Daniel Cristian Cruz > ... > -- Daniel Cristian Cruz クルズ クリスチアン ダニエル

Re: [BUGS] Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view

How about a warning in docs for uncautious DBA's? 2011/10/13 Bruce Momjian > > I assume this should _not_ be added as a TODO. -- Daniel Cristian Cruz クルズ クリスチアン ダニエル