Re: Check for interrupts in bf and xdes crypt()

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Andreas Karlsson <andreas(at)proxel(dot)se>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Check for interrupts in bf and xdes crypt()
Date: 2015-12-27 14:53:22
Message-ID: CAMkU=1yg97x03MQuLFWYcqqajucLZ=gMD9R9XRBFQ8JBNtk5SQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 15, 2015 at 12:35 AM, Andreas Karlsson <andreas(at)proxel(dot)se> wrote:
> Hi,
>
> Here is a patch which makes it possible to cancel a query which runs the
> crypt() function with the bf or xdes hashing algorithm, e.g. crypt('foo',
> gen_salt('bf', 13)). The md5 algorithm does not run for multiple rounds so
> there is no reason to patch it.
>
> I noticed this problem when I accidentally picked a too high n for the
> number of hash rounds.
>
> I have added a call to CHECK_FOR_INTERRUPTS() after every round, and I could
> not measure any performance hit from this.

Looks good to me. Applies, builds, passes make check, does what it
says and says what it does. No need for docs, no noticeable
performance impact.

I've marked it ready for committer. Also recommend for back-patching.

Cheers,

Jeff

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2015-12-27 15:50:47 Avoid endless futile table locks in vacuuming.
Previous Message Pavel Stehule 2015-12-27 07:11:50 Re: Add numeric_trim(numeric)