| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | khizer <khizer(at)srishtisoft(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com>, Robert Treat <rob(at)xzilla(dot)net> |
| Subject: | Re: postgresql-9.0 |
| Date: | 2012-02-15 19:50:25 |
| Message-ID: | CAOR=d=0Tbap8HSywUcew1tF8-Wnk0ntCuiLcHjj=ejb6q1O5XQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 14, 2012 at 11:29 PM, khizer <khizer(at)srishtisoft(dot)com> wrote:
> Hi,
> In postgresql 9.0.4 i connected to a database and trying to make
> queries but
> i am facing memory issue, getting err as glibc detected realloc
> invalid next size
> so kindly requesting u to provide your valuable feed backs
The first thing to figure out is if this is a client or server side
issue. It's not uncommon to see folks do something like:
psql mybigdb
select * from somebigtable;
and run out of memory on the client.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vossistemas | 2012-02-15 19:51:21 | conexão no windows 7 |
| Previous Message | Scott Marlowe | 2012-02-15 19:49:14 | Re: Table growing faster than autovacuum can vacuum |