Re: GIN improvements part 1: additional information

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GIN improvements part 1: additional information
Date: 2013-10-12 10:11:44
Message-ID: CAPpHfdvmYZqh=QdV+wrNyR+GJxS4gEH0gmKG4sTxeOfVxbcV_g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Oct 12, 2013 at 1:55 AM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:

> On 10.10.2013 13:57, Heikki Linnakangas wrote:
> > On 09.10.2013 02:04, Tomas Vondra wrote:
> >> On 8.10.2013 21:59, Heikki Linnakangas wrote:
> >>> On 08.10.2013 17:47, Alexander Korotkov wrote:
> >>>> Hi, Tomas!
> >>>>
> >>>> On Sun, Oct 6, 2013 at 3:58 AM, Tomas Vondra<tv(at)fuzzy(dot)cz> wrote:
> >>>>
> >>>>> I've attempted to rerun the benchmarks tests I did a few weeks ago,
> >>>>> but
> >>>>> I got repeated crashes when loading the data (into a table with
> >>>>> tsvector+gin index).
> >>>>>
> >>>>> Right before a crash, theres this message in the log:
> >>>>>
> >>>>> PANIC: not enough space in leaf page!
> >>>>>
> >>>>
> >>>> Thanks for testing. Heikki's version of patch don't works for me too
> on
> >>>> even much more simplier examples. I can try to get it working if he
> >>>> answer
> >>>> my question about GinDataLeafPageGetPostingList* macros.
> >>>
> >>> The new macros in that patch version were quite botched. Here's a new
> >>> attempt.
> >>
> >> Nope, still the same errors :-(
> >>
> >> PANIC: not enough space in leaf page!
> >> LOG: server process (PID 29722) was terminated by signal 6: Aborted
> >> DETAIL: Failed process was running: autovacuum: ANALYZE public.messages
> >
> > I've continued hacking away at the patch, here's yet another version.
> > I've done a lot of cleanup and refactoring to make the code more
> > readable (I hope). I'm not sure what caused the panic you saw, but it's
> > probably fixed now. Let me know if not.
>
> Yup, this version fixed the issues. I haven't been able to do any
> benchmarks yet, all I have is some basic stats
>
> | HEAD | patched
> ======================================
> load duration | 1084 s | 1086 s
> subject index | 96 MB | 96 MB
> body index | 2349 MB | 2051 MB
>
> So there's virtually no difference in speed (which is expected, AFAIK)
> and the large index on full message bodies is significantly smaller.

Yes, it should be no significant difference in speed. But difference in
index sizes seems to be too small. Could you share database dump somewhere?

------
With best regards,
Alexander Korotkov.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2013-10-12 15:14:26 Re: Compression of full-page-writes
Previous Message Magnus Hagander 2013-10-12 07:07:26 Re: Auto-tuning work_mem and maintenance_work_mem