Thank you, Tom.
But there's a problem, for which I hope you have
more wisdom. The reason why I tried that query
is because someone tried the same thing via odbc
from pc quering postgres database and got the
same error ("out of memory").
What can a pc user do? Anything?
Regards,
Tena
[EMAIL P
"Tena Sakai" <[EMAIL PROTECTED]> writes:
>> canon=3D# select * from public.genotype;
>> out of memory
> The version is 8.2.4 and platform is redhat linux
> on dell server. The table has 36 million rows.
Try \set FETCH_COUNT 1000
regards, tom lane
---
Hi Everybody,
I saw something I had never seen with psql.
> canon=#
> canon=# select * from public.genotype;
> out of memory
> [EMAIL PROTECTED] tws]$ echo $?
> 1
> [EMAIL PROTECTED] tws]$
The version is 8.2.4 and platform is redhat linux
on dell server. The table has 36 million rows.
I don'
[EMAIL PROTECTED] writes:
> How can I stop postmaster when it is in an uncontrollable state? If I
> cannot simply stop it by stopping the service (net stop), and I can't get
> to it through psql, what is the easiest way to stop it?
This question is too open-ended to have any simple answer. Ple
Tom Lane wrote:
Brian Staszewski <[EMAIL PROTECTED]> writes:
WARNING: oldest xmin is far in the past
HINT: Close open transactions soon to avoid wraparound problems.
Hmm ... which PG version is this? I think 8.2 will start to complain
about this much earlier than older versions (~ 1
How can I stop postmaster when it is in an uncontrollable state? If I
cannot simply stop it by stopping the service (net stop), and I can't get
to it through psql, what is the easiest way to stop it?
Thanks,
Patrick
The information contained in this communication is confidential, it is
inte
On Tue, Sep 11, 2007 at 12:26:18PM +, Mateus Interciso wrote:
> Thanks for your reply.
> Is there any way on PostgreSQL that I can see the transaction that
> haven't been commited?
The following queries shows open transactions and locks held by the
transaction.
select c.relname,l.transactio
On Tue, 11 Sep 2007 14:33:23 +0200, Thomas Markus wrote:
> check your jboss log for stack traces.
>
> Mateus Interciso schrieb:
>> Thanks for your reply.
>> Is there any way on PostgreSQL that I can see the transaction that
>> haven't been commited?
>>
>> This would simplify the debugging.
>>
>>
check your jboss log for stack traces.
Mateus Interciso schrieb:
Thanks for your reply.
Is there any way on PostgreSQL that I can see the transaction that
haven't been commited?
This would simplify the debugging.
Thanks a lot.
Mateus.
---(end of broadcast)-
On Tue, 11 Sep 2007 13:39:28 +0200, Tino Schwarze wrote:
> On Tue, Sep 11, 2007 at 11:15:54AM +, Mateus Interciso wrote:
>
>> Hello, it's been a while that I'm seeing that our servers running JBoss
>> with PostgreSQL, after some hours of work, have at least 70 or more
>> " in transaction" sta
On Tue, Sep 11, 2007 at 11:15:54AM +, Mateus Interciso wrote:
> Hello, it's been a while that I'm seeing that our servers running JBoss
> with PostgreSQL, after some hours of work, have at least 70 or more
> " in transaction" status for transactions, and this is bogging down
> our servers.
Hi,
it means that a transaction isn't finished (commit/rollback). check your
application for long running operations or programmming errors.
tm
Mateus Interciso schrieb:
Hello, it's been a while that I'm seeing that our servers running JBoss
with PostgreSQL, after some hours of work, have at
Hello, it's been a while that I'm seeing that our servers running JBoss
with PostgreSQL, after some hours of work, have at least 70 or more
" in transaction" status for transactions, and this is bogging down
our servers.
Is this normal behaviour? If not, is there anything I can do to prevent
it
13 matches
Mail list logo
