Re: [GENERAL] Basic Question on Point In Time Recovery

dopey. > > Is our current "frequent pg_dump" approach a sensible way to go about > things. Or are we missing something? Is there some other way to > restore one database without affecting the others? > > Thanks in advance. > > Robert. > -- Stéphane Schildknecht Contact régional PostgreSQL pour l'Europe francophone Loxodata - Conseil, expertise et formations 06.17.11.37.42 signature.asc Description: OpenPGP digital signature

Re: [GENERAL] pg_xlog on a hot_stanby slave

onf on the slave. That is "quite" correct when the streaming can't get WAL from the master. But cp is probably not the right tool. You also cp from the master archive directory, and are cleaning on that directory as well. You don't clean up the standby xlog directory. And c

Re: [GENERAL] Charging for PostgreSQL

On 06/01/2016 16:54, James Keener wrote: > As Melvin mentioned, this belongs in a new thread. And as such, it would have been really kind to actually start a new one. (...) -- Stéphane Schildknecht Contact régional PostgreSQL pour l'Europe francophone Loxodata - Conseil, expertise et fo

Re: [GENERAL] CoC [Final]

> > I would also vote in favour of not tolerating the behaviour. I guess it would be less open to critics than saying a participant is not tolerated... -- Stéphane Schildknecht Contact régional PostgreSQL pour l'Europe francophone Loxodata - Conseil, expertise et formati

[GENERAL] Excluding schema from backup

hen got "pg_dump: No matching schemas were found" Dumping the only public schema works. But, by doing so, I miss some other schema I really need. Is there a limitation I didn't catch ? Thanks by advance. Stéphane Schildknecht ---(end of broadcast)

[GENERAL] FK Constraint on index not PK

aint... Thanks by advance Stéphane Schildknecht ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [GENERAL] FK Constraint on index not PK

Scott Marlowe a écrit : > Being quite familiar with both of those issues from the past, I can't > imagine either one causing a problem with an update prior to dumping so > he can then upgrade to 8.2. > > Seriously. Hungarian collation, plerl can no longer change locale and > corrupt indexes, and a

Re: [GENERAL] FK Constraint on index not PK

Joshua D. Drake a écrit : > On Fri, 2007-01-12 at 17:50 +0100, Stéphane Schildknecht wrote: > >> Dear community members, >> >> I'm having a quite strange behaviour while trying to drop some index. >> >> We have some tables with two indexes on a primar

Re: [GENERAL] FK Constraint on index not PK

Tom Lane a écrit : > =?UTF-8?B?U3TDqXBoYW5lIFNjaGlsZGtuZWNodA==?= <[EMAIL PROTECTED]> writes: > >> My goal is to migrate to 8.2.1. definitely. But as you said it, I do not >> want to recreate unwanted index when migrating. I want to drop them BEFORE. >> But, I can't just do a "drop index" comman

[GENERAL] pg_dump without oids

o have #default_with_oids = off in postgresql.conf for 8.2. Is there a way to prevent creating table with oids ? A table created by psql client is created without OID. Thanks by advance Stéphane Schildknecht ---(end of broadcast)--- TIP 9: In versio

Re: [GENERAL] Who is Slony Master/Slave + general questions.

Hello, You should ask directly to the slony1 mailing list. [EMAIL PROTECTED] a écrit : > (...) The Slony version I'm using is 1.1.2. The current version of Slony1 is slony1-1.2.6. > Take a scenario that > you want to check the state of the system without prior knowledge of > the node setup, how w

[GENERAL] Timestamp precision

o with a microsecond precision ;-) Best regards, -- Stéphane SCHILDKNECHT Président de PostgreSQLFr http://www.PostgreSQLFr.org ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail comman

[GENERAL] Number format problem

lem occurs under Ubuntu Breezy and Debian Testing. My current configuration is [EMAIL PROTECTED] client_encoding=LATIN9 server_encoding=LATIN9 I tried to reconfigure locales and restart the server, but I can't get the result I expect. I really don't know what else I could do. Sin

[GENERAL] Number format problem

lem occurs under Ubuntu Breezy and Debian Testing. My current configuration is [EMAIL PROTECTED] client_encoding=LATIN9 server_encoding=LATIN9 I tried to reconfigure locales and restart the server, but I can't get the result I expect. I really don't know what else I could do. Sin