Re: [BUGS] BUG #5713: lo_export

2010-10-16 Thread Alvaro Herrera
Excerpts from Ionut Berlea's message of sáb oct 16 06:56:54 -0300 2010: > How can i use lo_export from client side to export the stored file into > client hdd? > In the locahost hdd is working but not at the client side. Please don't use the bug report form to ask questions. Instead, you could s

Re: [BUGS] BUG #5712: pg_dump for one table specified schema

2010-10-16 Thread Craig Ringer
On 10/16/2010 05:31 PM, Ionut Berlea wrote: What will be the right sintax Please don't use the bug report form for help questions. You could ask for help on the EnterpriseDB forums if you prefer web forums, or on the pgsql-general mailing list. http://www.postgresql.org/community/lists/ -

[BUGS] Empty bytea format - 9.1devel pg_dump and psql

2010-10-16 Thread Vladimir Kokovic
Hi, I'm not sure whether it is OK, a blank format for bytea, which is presented in 9.1devel (pg_dump and psql) Earlier versions (7, 8): psql - signature bytea not null default '':: bytea pg_dump - signature bytea default ''::bytea not null postgresql.conf: standard_conforming_strings = off bytea

[BUGS] BUG #5713: lo_export

2010-10-16 Thread Ionut Berlea
The following bug has been logged online: Bug reference: 5713 Logged by: Ionut Berlea Email address: ionutber...@gmail.com PostgreSQL version: 9.0 Operating system: Windows 7 Description:lo_export Details: Hi, How can i use lo_export from client side to export the

[BUGS] BUG #5712: pg_dump for one table specified schema

2010-10-16 Thread Ionut Berlea
The following bug has been logged online: Bug reference: 5712 Logged by: Ionut Berlea Email address: ionutber...@gmail.com PostgreSQL version: 9.0 Operating system: Windows 7 Description:pg_dump for one table specified schema Details: Hi, I try to pg_dump one table

Re: [BUGS] problem with glibc strerror messages translation

2010-10-16 Thread Craig Ringer
On 10/16/2010 08:58 PM, Robert Haas wrote: 2010/10/13 Sergey Burladyan: IMHO you can receive question-marks here if lc_messages in postgresql.conf do not match with locale from environment at server start, for example: correctly translated and displayed: $ LANG=ru_RU.UTF-8 ../bin/postgres -D d

Re: problem with glibc strerror messages translation (was: [BUGS] Could not open file pg_xlog/000000010....)

2010-10-16 Thread Robert Haas
2010/10/13 Sergey Burladyan : > Tom Lane writes: > >> Victor writes: >> > Oct 12 17:53:25 localhost postgres[26997]: [1753-1] PANIC:  could not >> > open file "pg_xlog/00010007" (log file 0, segment >> > 7): >> >> Hm, where's the rest of that error message?