Re: [ADMIN] bad data with Foreign Key constraint

"Lee Wu" <[EMAIL PROTECTED]> writes: > I have found that there are some foreign keys in our detail tables while > there are not primary keys in master tables. > Yes, we have FK constraints on detail tables. > I could not think how it can happen. PG (7.3.2) does not have "disable > constraint" like

Re: [ADMIN] table when vacuum questions

Thanks Tom for your quick response... -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Friday, June 18, 2004 3:26 PM To: Lee Wu Cc: [EMAIL PROTECTED] Subject: Re: [ADMIN] table when vacuum questions "Lee Wu" <[EMAIL PROTECTED]> writes: > http://www.postgresql.org/docs/

[ADMIN] bad data with Foreign Key constraint

Hi All,   I have found that there are some foreign keys in our detail tables while there are not primary keys in master tables. Yes, we have FK constraints on detail tables. I could not think how it can happen. PG (7.3.2) does not have “disable constraint” like Oracle, does it?   Samp

Re: [ADMIN] table when vacuum questions

"Lee Wu" <[EMAIL PROTECTED]> writes: > http://www.postgresql.org/docs/7.3/static/routine-vacuuming.html#VACUUM- > FOR-WRAPAROUND says: > "every table in the database must be vacuumed at least once every > billion transactions". > Does "very table" include PG's tables, such as pg_database? Yes, a

[ADMIN] table when vacuum questions

Hi,   I have two questions regarding the PG doc:   http://www.postgresql.org/docs/7.3/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND says:  “every table in the database must be vacuumed at least once every billion transactions”. Does “very table” include PG’s tables, suc

Re: [ADMIN] pg_restore patch

"Lee Wu" <[EMAIL PROTECTED]> writes: >> Why don't you just update to 7.3.6, instead? > I have already recommended to upgrade to 7.4. However, it is not me > to make the decision. Also, we have some resellers running 7.3.2 in > production environments too and I am not sure whether they are willing

Re: [ADMIN] pg_class corrupted ?

I wrote: > Bruno THOMAS <[EMAIL PROTECTED]> writes: >> My problem is that when I tried to make a dump of the copied DB for a >> new backup I've had the following error : >> pg_dump: query to obtain list of tables failed: ERROR: Relation >> pg_class does not have attribute 1 > Reindexing pg_clas

Re: [ADMIN] pg_restore patch

Thanks Tom! I have already recommended to upgrade to 7.4. However, it is not me to make the decision. Also, we have some resellers running 7.3.2 in production environments too and I am not sure whether they are willing to upgrade. -Original Message- From: Tom Lane [mailto:[EMAIL PROTE

Re: [ADMIN] pg_restore patch

"Lee Wu" <[EMAIL PROTECTED]> writes: > Can this patch apply to 7.3.2? Why don't you just update to 7.3.6, instead? regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister comma

Re: [ADMIN] pg_class corrupted ?

Bruno THOMAS <[EMAIL PROTECTED]> writes: > My problem is that when I tried to make a dump of the copied DB for a > new backup I've had the following error : > pg_dump: query to obtain list of tables failed: ERROR: Relation > pg_class does not have attribute 1 Reindexing pg_class might help. Re

Re: [ADMIN] [Support i5GKDLjR008723] PGRES_FATAL_ERROR: out of free buffers:

"David F. Skoll" <[EMAIL PROTECTED]> writes: > Hi, Jochen. >> However, we frequently observe the following message in the log files: >> PGRES\_FATAL_ERROR : ERROR: out of free buffers: time to abort! >> Any hints what's going on? Suggestion? IIRC, there was a problem in 7.3 - 7.3.2 that tended to