"Amos"
This is not a bug. Your PostgreSQL install is misconfigured - you have
told it to use more memory than you have. Use a reasonable number of
max_connections, maybe as few as 20 or 30, and set c3p0 (your connection
pooler) to use one or two fewer than that. Your webapp's clients should
share
The following bug has been logged online:
Bug reference: 5756
Logged by: amos
Email address: amosl...@gmail.com
PostgreSQL version: 8.3
Operating system: windows server 2008
Description:postgres eat up all memory(2GB memory)
Details:
Hi:
I am sorry for not good at e
On Tue, Nov 16, 2010 at 10:48 AM, Jon Nelson wrote:
> I have a process which runs in parallel creating tables which, as the
> /final/ step in the import, gets SQL much like the following applied:
>
> ALTER TABLE foo INHERIT bar;
>
> Periodically, I get this error: tuple concurrently updated
>
> O
On Tue, Nov 16, 2010 at 5:13 PM, Kris Jurka wrote:
> On Tue, 16 Nov 2010, Korry Douglas wrote:
>
>> Vince - is there any chance that you were using a non-standard PostgreSQL
>> distribution or driver before? Like something from EnterpriseDB? It may be
>> that a third-party JDBC driver was doing
On 17.11.2010 18:05, Tom Lane wrote:
"Elliott Groszek" writes:
The following SQL statements produce different query plans even though
"phone" is not reference in the SQL!
explain update customer set login_name =
(select "NESSOuserName" from person,phone
where person.cac_cert=customer.cac_cer
"Elliott Groszek" writes:
> The following SQL statements produce different query plans even though
> "phone" is not reference in the SQL!
> explain update customer set login_name =
> (select "NESSOuserName" from person,phone
> where person.cac_cert=customer.cac_cert);
> explain update customer s
The following bug has been logged online:
Bug reference: 5755
Logged by: Elliott Groszek
Email address: elliott.gros...@navy.mil
PostgreSQL version: 8.4.4
Operating system: RedHat
Description:Query Optimzer Bug
Details:
The following SQL statements produce different
