Skip site navigation (1) Skip section navigation (2)

BUG #2260: PGCrypto Memory Problem

From: "Daniel Blaisdell" <lunk(dot)djedi(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2260: PGCrypto Memory Problem
Date: 2006-02-14 17:28:25
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      2260
Logged by:          Daniel Blaisdell
Email address:      lunk(dot)djedi(at)gmail(dot)com
PostgreSQL version: 8.1.2
Operating system:   Gentoo Linux K:2.6.9
Description:        PGCrypto Memory Problem


Table Setup:
employeeid integer
salt text
md5password text

Problem Query:
select * from table where md5password = crypt('password',salt)

The first time this query is run, I see the postgres process bump up to 8MB
of ram from where it initializes.

On subsequent issues of the same query the postgres's process memory
footprint grows each time.

Initial Memory Usage (from Top)
13463 postgres  17   0 17556 4716  15m S  0.0  0.5   0:00.00 postgres:
postgres fh_dev [local] idle
Initial RSS: 4716

After 1st Query Run:
13570 postgres  16   0 91120  78m  15m S  0.0  8.8   0:01.22 postgres:
postgres fh_dev [local] idle
RSS: 78M

After 2nd Query Run:
13570 postgres  16   0  160m 149m  15m S  0.0 17.0   0:02.60 postgres:
postgres fh_dev [local] idle
RSS: 149M

After 3rd Query Run:
13570 postgres  16   0  232m 221m  15m S 30.9 25.1   0:03.83 postgres:
postgres fh_dev [local] idle
RSS: 232M

4th Query Run:
RSS: 293M

And so on and so forth until all swap space is eaten up.

Hope someone knows what's going on here, i'd love to be able to use the
pgcrypto contribs in production.



pgsql-bugs by date

Next:From: Evgeny GridasovDate: 2006-02-14 17:39:46
Subject: BUG #2261: ILIKE seems to be buggy on koi8 input
Previous:From: Tom LaneDate: 2006-02-14 17:22:44
Subject: Re: BUG #2257: Can' stop server while autovacuum is running

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group