The following bug has been logged online:
Bug reference: 2576
Logged by: Fujii Masao
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Fedora Core 5
Description:tcp_keepalive doesn't work
Details:
Hi.
I found an error that tcp_keepalive d
"Fujii Masao" <[EMAIL PROTECTED]> writes:
> I found an error that tcp_keepalive doesn't work.
You seem to have a misunderstanding of what tcp_keepalive is for. It
does not kill a backend that is in the midst of a query. A backend will
terminate when it is waiting for a client command and it sees
Hi, my problem was problably corrupted index files. I recreated the index and it's ok now. The hardware was being unpluged from power source without shuthing down, I guess that's the cause.I used the fallowing commands to recreate index:
/etc/init.d/postgresql stop
su postgres
/usr/lib/postgresql/b
Hello,
i have a statement which ends with
ERROR: out of memory
DETAIL: Failed on request of size 639.
i tried it several times, the number after size changes but not the outcome.
could someone tell me what information you need to tell me whats wrong?
what i have so fare is:
PostgreSQL ver
The following bug has been logged online:
Bug reference: 2577
Logged by: niktto
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7-4-7
Operating system: debian
Description:Notice: Only variable references should be retur..
Details:
What is? :(
Notice: Only var
On Tue, Aug 15, 2006 at 03:36:24PM +, niktto wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2577
> Logged by: niktto
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7-4-7
> Operating system: debian
> Description:Notice: Only varia
"Anita Lederer" <[EMAIL PROTECTED]> writes:
> i have a statement which ends with
> ERROR: out of memory
> DETAIL: Failed on request of size 639.
Do you have work_mem set to a large value? Your query plan contains
several sorts so would potentially try to use several times work_mem
... if th
Hi.
> You seem to have a misunderstanding of what tcp_keepalive is for. It
> does not kill a backend that is in the midst of a query. A backend will
> terminate when it is waiting for a client command and it sees that the
> connection has been lost --- which is what a TCP timeout will cause to
>
