Re: [HACKERS] set_client_encoding is broken

2009-08-31 Thread Tom Lane
Zdenek Kotala writes: > Tom Lane píše v po 31. 08. 2009 v 11:00 -0400: >> I'm leaning to the third choice, but I wonder if anyone has any >> comments or better ideas. > It seems to me that 3 is OK. > Another possibility is that InitPostgres can only fill up rel cache and > GUC processing can s

Re: [HACKERS] set_client_encoding is broken

2009-08-31 Thread Zdenek Kotala
Tom Lane píše v po 31. 08. 2009 v 11:00 -0400: > 3. Push the startup-packet GUC processing (approx. lines 3340..3395 of > postgres.c, as of CVS HEAD) into InitPostgres, so it can be run during > the startup transaction. This is not too unclean, though it would > mean exporting process_postgres_sw

Re: [HACKERS] set_client_encoding is broken

2009-08-31 Thread Tom Lane
Zdenek Kotala writes: > [4a9ae815.696e:1] LOG: connection received: host=[local] > [4a9ae815.696e:2] LOG: connection authorized: user=postgres database=postgres > [4a9ae815.696e:3] LOG: conversion between UTF8 and LATIN2 is not supported > [4a9ae815.696e:4] FATAL: invalid value for parameter "

[HACKERS] set_client_encoding is broken

2009-08-31 Thread Zdenek Kotala
If you look on gothic_moth and comet_moth http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=gothic_moth&dt=2009-08-30%2020:06:00 http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=comet_moth&dt=2009-08-29%2021:06:00 you can see following error: ../../src/test/regress/pg_regress --inputdir=. --psq