Josh Berkus writes:
>> tarr[1] does not have a \, because it was eaten by the parser (so \y is
>> the same as a plain y). tarr[2] does have a single backslash, which for
>> output purposes is shown escaped with another backslash when part of an
>> array, but unescaped when not. I'm not sure if t
Alvaro,
> tarr[1] does not have a \, because it was eaten by the parser (so \y is
> the same as a plain y). tarr[2] does have a single backslash, which for
> output purposes is shown escaped with another backslash when part of an
> array, but unescaped when not. I'm not sure if this qualifies as
Josh Berkus wrote:
> When saving \ escaped values into text array fields, the \ is escaped when
> displaying the contents of the array, leading to an appearance that the
> correct data was not saved:
>
> scratch=# create table test_arr ( tarr text[] );
> CREATE TABLE
> scratch=# insert into tes
Issue: \ is escaped oddly when displaying the contents of array fields.
Severity: annoyance
Affects: 8.1.3, 8.1.4, 8.0.3, possibly others.
Demonstration of bug:
When saving \ escaped values into text array fields, the \ is escaped when
displaying the contents of the array, leading to an appearan
Is this the correct list to report issues with the www.postgresql.org
website and it's related sites? If not, I apologize, could someone
point me in the right direction?
There seems to be a problem with list archive searching, the result
set item links do not always point to the actual messag
Fujii Masao <[EMAIL PROTECTED]> writes:
> Linux-Kernel Archive: Re: 2.6.12.5 bug? per-socket TCP keepalive settings
> http://www.ussg.iu.edu/hypermail/linux/kernel/0508.2/0757.html
> I'm confused whether tcp_keepalive problem should be solved
> at the DB level.
According to that, Linux keepalive
> Bug reference: 2548
> Logged by: Ricardo Solanilla
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.3
> Operating system: Windows XP Pro
> Description:Fatal error with timezone
> Details:
>
> my log show this error, the server stop and never more i could
Hi.
I found the cause of the error that tcp_keepalive doesn't work.
The cause is a specification of linux kernel.
In the specification of linux kernel, tcp_keepalive doesn't work
if the network outage occurs before receiving ACK for send() system-call.
This behavior of tcp_keepalive is reported e
