On 11/30/06, hubert depesz lubaczewski <[EMAIL PROTECTED]> wrote:
On 11/30/06, Teodor Sigaev <[EMAIL PROTECTED]> wrote:
>
> Fixed, thank you. Changes are commited in CVS, pls, try it (I think that
> index
> is corrupted, so you need to recreate it)
great. thanks. i will retry. full retry will t
On 11/30/06, Teodor Sigaev <[EMAIL PROTECTED]> wrote:
Fixed, thank you. Changes are commited in CVS, pls, try it (I think that
index
is corrupted, so you need to recreate it)
great. thanks. i will retry. full retry will take some time - i can
estimate that i will be able to reply tomorrow in
Fixed, thank you. Changes are commited in CVS, pls, try it (I think that index
is corrupted, so you need to recreate it)
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
-
I reproduce a problem with small script:
print <5000 and i<40;
VACUUM FULL ANALYZE qq;
EOT
So, I'm digging now...
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
--
Teodor Sigaev <[EMAIL PROTECTED]> writes:
>> #1 0x080bc224 in PageDeletePostingItem (page=0xb28039a0 "\020",
>> offset=53719) at gindatapage.c:291
>> #2 0x080bf558 in ginDeletePage (gvs=0xbfc2ab80, deleteBlkno=29194,
>> leftBlkno=29059, parentBlkno=70274, myoff=351, isParentRoot=0 '\0') at
>>
#1 0x080bc224 in PageDeletePostingItem (page=0xb28039a0 "\020",
offset=53719) at gindatapage.c:291
#2 0x080bf558 in ginDeletePage (gvs=0xbfc2ab80, deleteBlkno=29194,
leftBlkno=29059, parentBlkno=70274, myoff=351, isParentRoot=0 '\0') at
ginvacuum.c:268
Are you sure about your hardware? myoff
On 11/30/06, Teodor Sigaev <[EMAIL PROTECTED]> wrote:
gdb /usr/local/pgsql/bin/postgres your_core_file
If it's needed, change path to postgres file.
In gdb, type
# bt
and send output
sure, here you have:
$ gdb /home/pgdba/work/bin/postgres /home/pgdba/data/core
GNU gdb 6.3-debian
Copyright 20
While I'm downloading your file, pls, do follow:
gdb /usr/local/pgsql/bin/postgres your_core_file
If it's needed, change path to postgres file.
In gdb, type
# bt
and send output
hubert depesz lubaczewski wrote:
hi,
i have been testing 8.2 rc1, while i got this problem.
base data:
linux, 32bit
hi,
i have been testing 8.2 rc1, while i got this problem.
base data:
linux, 32bit, kernel: 2.6.18.3; debian
postgresql version:
PostgreSQL 8.2rc1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC)
3.3.5(Debian 1:
3.3.5-13)
problematic table is over 2gigabytes in size, and has several indices - one
