Re: Patch for fast gin cache performance improvement

From: Ian Link <ian(at)ilink(dot)io>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Kevin Grittner <kgrittn(at)ymail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch for fast gin cache performance improvement
Date: 2013-06-23 09:28:04
Message-ID: 51C6BFA4.4040003@ilink.io
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I just tried it and my account works now. Thanks!
Ian

> Stefan Kaltenbrunner <mailto:stefan(at)kaltenbrunner(dot)cc>
> Sunday, June 23, 2013 2:05 AM
>
> have you tried to log in once to the main website per:
>
> http://www.postgresql.org/message-id/CABUevEyt9tQfcF7T2Uzcr8WeF9M=s8qSACuCmN5L2Et26=RTjw@mail.gmail.com
>
> ?
>
>
> Stefan
> ian link <mailto:ian(at)ilink(dot)io>
> Saturday, June 22, 2013 7:03 PM
> Looks like my community login is still not working. No rush, just
> wanted to let you know. Thanks!
>
> Ian
>
>
>
> Ian Link <mailto:ian(at)ilink(dot)io>
> Tuesday, June 18, 2013 11:41 AM
>
> No worries! I'll just wait until it's up again.
> Thanks
> Ian
> Kevin Grittner <mailto:kgrittn(at)ymail(dot)com>
> Tuesday, June 18, 2013 9:15 AM
>
> Oops -- we seem to have a problem with new community logins at the
> moment, which will hopefully be straightened out soon. You might
> want to wait a few days if you don't already have a login.
>
> --
> Kevin Grittner
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
> Kevin Grittner <mailto:kgrittn(at)ymail(dot)com>
> Tuesday, June 18, 2013 9:09 AM
> Ian Link<ian(at)ilink(dot)io> wrote:
>
>> This patch contains a performance improvement for the fast gin
>> cache.
>
>> Our test queries improve from about 0.9 ms to 0.030 ms.
>
> Impressive!
>
>> Thanks for reading and considering this patch!
>
> Congratulations on your first PostgreSQL patch! To get it
> scheduled for review, please add it to this page:
>
> https://commitfest.postgresql.org/action/commitfest_view/open
>
> You will need to get a community login (if you don't already have
> one), but that is a quick and painless process. Choose an
> appropriate topic (like "Performance") and reference the message ID
> of the email to which you attached the patch. Don't worry about
> the fields for reviewers, committer, or date closed.
>
> Sorry for the administrative overhead, but without it things can
> fall through the cracks. You can find an overview of the review
> process with links to more detail here:
>
> http://wiki.postgresql.org/wiki/CommitFest
>
> Thanks for contributing!
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2013-06-23 09:45:09 Re: A better way than tweaking NTUP_PER_BUCKET
Previous Message Stefan Kaltenbrunner 2013-06-23 09:05:35 Re: Patch for fast gin cache performance improvement