[BUGS] data loss with pg_standby when doing a controlled failover

Running 8.3.7, I have a warm standby configuration with a archive_timeout of 10min. It's obvious that there's a 10min period where data could be lost if the master fails and the warm standby server has to take over. What's not obvious is that this is true even if the master server is shut down reg

[BUGS] length() return wrong result

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, - From the documentation, length(string) is 'Number of characters in string' But it didn't : 1/ in a LATIN9 database: postgres=# show server_encoding; server_encoding - - LATIN9 postgres=# set client_encoding = utf8; SET post

Re: [BUGS] length() return wrong result

Cédric Villemain wrote: - From the documentation, length(string) is 'Number of characters in string' But it didn't : 1/ in a LATIN9 database: postgres=# show server_encoding; server_encoding - - LATIN9 postgres=# set client_encoding = utf8; SET postgres=# select length('é');

Re: [BUGS] data loss with pg_standby when doing a controlled failover

On Mon, Apr 6, 2009 at 7:37 AM, Andreas Pflug wrote: > Running 8.3.7, I have a warm standby configuration with a > archive_timeout of 10min. > > It's obvious that there's a 10min period where data could be lost if the > master fails and the warm standby server has to take over. What's not > obviou

Re: [BUGS] data loss with pg_standby when doing a controlled failover

On Mon, Apr 6, 2009 at 1:37 PM, Andreas Pflug wrote: > IMHO this should be mentioned in the docs explicitly (I find it quite > surprising that data can be lost even if the system is shutdown > correctly), or better when shutting down the postmaster should spit all > log segments containing all cha

[BUGS] BUG #4750: UPDATE called from PL/pgSQL failed when there is ON UPDATE DO INSTEAD NOTHING rule

The following bug has been logged online: Bug reference: 4750 Logged by: Ondrej Novy Email address: on...@netbox.cz PostgreSQL version: 8.2.13 Operating system: Linux Description:UPDATE called from PL/pgSQL failed when there is ON UPDATE DO INSTEAD NOTHING rule Detail

Re: [BUGS] data loss with pg_standby when doing a controlled failover

Scott Mead wrote: > > > > On Mon, Apr 6, 2009 at 7:37 AM, Andreas Pflug > mailto:pgad...@pse-consulting.de>> wrote: > > Running 8.3.7, I have a warm standby configuration with a > archive_timeout of 10min. > > It's obvious that there's a 10min period where data could be lost > if th

Re: [BUGS] data loss with pg_standby when doing a controlled failover

Guillaume Smet wrote: > On Mon, Apr 6, 2009 at 1:37 PM, Andreas Pflug > wrote: > >> IMHO this should be mentioned in the docs explicitly (I find it quite >> surprising that data can be lost even if the system is shutdown >> correctly), or better when shutting down the postmaster should spit al

Re: [BUGS] BUG #4750: UPDATE called from PL/pgSQL failed when there is ON UPDATE DO INSTEAD NOTHING rule

"Ondrej Novy" writes: > Description:UPDATE called from PL/pgSQL failed when there is ON > UPDATE DO INSTEAD NOTHING rule This is fixed for 8.4, but the fix was deemed too invasive to back-patch into existing branches. regards, tom lane -- Sent via pgsql-bugs mai

[BUGS] PostgreSQL 8.3.7: soundex function returns UTF-16 characters

Hello, We have just discovered a problem with the soundex function in PostgreSQL 8.3.7. The problem is easy to reproduce. The following query returns the ASCII code of the soundex representation of the Greek letter Pi: select ascii (soundex('Π')); In PostgreSQL 8.2.6 the result would be 0 (c

Re: [BUGS] PostgreSQL 8.3.7: soundex function returns UTF-16 characters

Frans writes: > We have just discovered a problem with the soundex function in > PostgreSQL 8.3.7. The problem is easy to reproduce. The following query > returns the ASCII code of the soundex representation of the Greek letter Pi: > select ascii (soundex('Π')); > In PostgreSQL 8.2.6 the resu

Re: [BUGS] PostgreSQL 8.3.7: soundex function returns UTF-16 characters

Tom Lane wrote: Frans writes: We have just discovered a problem with the soundex function in PostgreSQL 8.3.7. The problem is easy to reproduce. The following query returns the ASCII code of the soundex representation of the Greek letter Pi: select ascii (soundex('Î '));

Re: [BUGS] PostgreSQL 8.3.7: soundex function returns UTF-16 characters

Frans writes: > Tom Lane wrote: >> The >> fuzzystrmatch module doesn't really work with utf8 (nor any other >> multibyte encoding), because it depends on the functions. >> What you'll probably get when applying it to non-ascii utf8 is >> an invalidly encoded string. >> > Well, in 8.2.6 the resul

Re: [BUGS] BUG #4751: Incorrect pg_dump output when dropping not null in inherited table.

"Grzegorz Junka" writes: > I don't know if these steps below are allowed, but documentation doesn't say > anything that they are not. > create table parent_table (someint integer not null); > create table child_table (id integer) inherits (parent_table); > alter table only child_table alter colum

[BUGS] BUG #4751: Incorrect pg_dump output when dropping not null in inherited table.

The following bug has been logged online: Bug reference: 4751 Logged by: Grzegorz Junka Email address: x...@poczta.onet.pl PostgreSQL version: 8.3.7 Operating system: FreeBSD 7.1 Description:Incorrect pg_dump output when dropping not null in inherited table. Details:

Re: [BUGS] data loss with pg_standby when doing a controlled failover

Hi, On Mon, Apr 6, 2009 at 11:13 PM, Andreas Pflug wrote: > Scott Mead wrote: >> >> >> >> On Mon, Apr 6, 2009 at 7:37 AM, Andreas Pflug >> mailto:pgad...@pse-consulting.de>> wrote: >> >>     Running 8.3.7, I have a warm standby configuration with a >>     archive_timeout of 10min. >> >>     It's