Hi there,
I set 'log_error_verbosity' to 'verbose' and I get the following message
logs:
2007-03-20 11:30:11 WARNING: 22P06: nonstandard use of \\ in a string
literal at character 128
2007-03-20 11:30:11 HINT: Use the escape string syntax for backslashes,
e.g., E'\\'.
2007-03-20 11:30:11 LOC
"Sabin Coanda" <[EMAIL PROTECTED]> writes:
> I set 'log_error_verbosity' to 'verbose' and I get the following message
> logs:
> 2007-03-20 11:30:11 WARNING: 22P06: nonstandard use of \\ in a string
> literal at character 128
> Is any chance to identify the source of these messages ?
log_min_er
Hi there,
I try to use WAL support for backup/recovery on Windows.
I applied the procedures from PostgreSQL 8.2.3 Documentation / 23.3.3.
Recovering using a Continuous Archive Backup.
I set the following archive commands:
- archive_command = 'copy "%p" "D:/Program
Files/PostgreSQL/8.2/test_sab
Hi for all,
I just installed Tsearch and was trying to configure automatic update on
such table using trigger and procedure.
But I get error on inserting data on the table.
Could you help me to find out what I am wronging?
Procedure created:
create or replace function fn_atualiza_tsearch_cid
Hi,
I am using postgres 8.2.3. I have recently converted my database from
sql-ascii to UTF8. I have a portal which calls a perl program to insert the
data into the database.
While inserting, I am getting an error message
DBD::Pg::st execute failed: ERROR: invalid byte sequence for en
I am using postgres 8.2.3. I have recently converted my database from
sql-ascii to UTF8. I have a portal which calls a perl program to insert the
data into the database.
While inserting, I am getting an error message
DBD::Pg::st execute failed: ERROR: invalid byte sequence for encoding
Am Dienstag, 20. März 2007 20:34 schrieb Karthikeyan Sundaram:
> Hi,
>
>I am using postgres 8.2.3. I have recently converted my database from
> sql-ascii to UTF8. I have a portal which calls a perl program to insert
> the data into the database.
>
> While inserting, I am getting an error
Sabin Coanda wrote:
> Hi there,
>
> I'd like to use WAL, but I need some clarifications about the
> backup/recovery procedure.
>
> In Postgresql v8.2.3 documentation, I found I have to make backup between
> pg_start_backup/pg_stop_backup executions, using tar/cpio tools.
>
> May I use pg_dumpa
I'm getting really mad at RHEL 4. They do not package a recent
postgres in the base distro, and only put 8.1.x in a disk call
lamp-beta... So now I wonder what a 'recommended' way of running
postgresql is -- meaning, any linux distro will do, just build it --
or is there any particular distro that
On Tue, Mar 20, 2007 at 09:06:35PM -0400, Joshua Kramer wrote:
>
> David,
>
> >I'm getting really mad at RHEL 4. They do not package a recent
> >postgres in the base distro, and only put 8.1.x in a disk call
> >lamp-beta... So now I wonder what a 'recommended' way of running
> >postgresql is -- m
David,
I'm getting really mad at RHEL 4. They do not package a recent
postgres in the base distro, and only put 8.1.x in a disk call
lamp-beta... So now I wonder what a 'recommended' way of running
postgresql is -- meaning, any linux distro will do, just build it --
Why not just download the
On Tue, Mar 20, 2007 at 09:06:25PM +0100, Claus Guttesen wrote:
> >DBD::Pg::st execute failed: ERROR: invalid byte sequence for encoding
> >"UTF8": 0x92
> >[for Statement "INSERT INTO longdescs (bug_id, who, bug_when, thetext,
> >isprivate)
>
> Try to modify client_encoding in postgresql.conf to
Hi,
On Tue, 2007-03-20 at 17:50 -0700, David Bear wrote:
> I'm getting really mad at RHEL 4. They do not package a recent
> postgres in the base distro, and only put 8.1.x in a disk call
> lamp-beta...
This is quite normal. Red Hat "Enterprise Linux" does not apply major
upgrades. For example, RH
13 matches
Mail list logo