On 07/04/2008, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Pavel Stehule escribió:
>
>
> > WARNING: problem in alloc set MessageContext: req size > alloc size
> > for chunk 0x8b6d1e0 in block 0x8b6bb50
> > WARNING: problem in alloc set MessageContext: req size > alloc size
> > for chunk 0x8b6
Pavel Stehule escribió:
> WARNING: problem in alloc set MessageContext: req size > alloc size
> for chunk 0x8b6d1e0 in block 0x8b6bb50
> WARNING: problem in alloc set MessageContext: req size > alloc size
> for chunk 0x8b6d1e0 in block 0x8b6bb50
I suggest you make distclean and rebuild the whol
On 07/04/2008, Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
> Pavel Stehule wrote:
>
> > when I tested ptop, I found some problems
> >
>
> Which version are you running?
I am sorry, HEAD 8.4 today actualized
Pavel
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
>
Pavel Stehule wrote:
when I tested ptop, I found some problems
Which version are you running?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.
Hello
when I tested ptop, I found some problems
this pgbench is very slow and when after getting table of locks from
ptop I got backend crash.
[EMAIL PROTECTED] ~]$ /usr/local/pgsql/bin/pgbench -c80 -t1000 postgres
starting vacuum...end.
WARNING: you don't own a lock of type ShareLock
WARNING:
