Re: Big insert/delete memory problems - Mailing list pgsql-general

Darn it, I knew I forgot something.  I'm running on redhat 7.3, with
postgresql version 7.3.2, accessing it through tomcat 4.1.18.  It
APPEARS that its the insert that bumps the memory.  Here's the schema
for the member table:


          Column         |           Type           |
   Modifiers
------------------------+--------------------------+---------------------------------------------------
  id                     | integer                  | not null default
nextval('"member_id_seq"'::text)
  username               | character varying(16)    | not null
  password               | character varying(16)    | not null
  email                  | character varying(255)   | not null
  firstname              | character varying(32)    | not null
  lastname               | character varying(32)    | not null
  address1               | character varying(100)   | default ''
  address2               | character varying(100)   | default ''
  address3               | character varying(100)   | default ''
  city                   | character varying(50)    | default ''
  state                  | character varying(10)    | default ''
  zipcode                | character varying(10)    | default ''
  telephone              | character varying(20)    | default ''
  fax                    | character varying(20)    | default ''
  imname                 | character varying(50)    | default ''
  implatform             | character varying(20)    | default ''
  gender                 | character(1)             |
  birthdate              | date                     |
  notifycampaigns        | boolean                  | default false
  notifytasks            | boolean                  | default false
  notifypoints           | boolean                  | default false
  notifyrewards          | boolean                  | default false
  contactemail           | boolean                  | default false
  contactim              | boolean                  | default false
  contactmail            | boolean                  | default false
  contacttelephone       | boolean                  | default false
  contactmembers         | boolean                  | default false
  receivecampaignresults | boolean                  | default false
  receivenewsletter      | boolean                  | default false
  educationlevel         | character varying(30)    | default ''
  studentorworking       | character varying(10)    | default ''
  companyname            | character varying(50)    | default ''
  title                  | character varying(50)    | default ''
  studentlevel           | character varying(30)    |
  implatformother        | character varying(20)    | default ''
  signedup               | timestamp with time zone | default
"timestamp"('now'::text)
  flags                  | character(20)            | default
'00000000000000000000'
  last_login             | timestamp with time zone | default
"timestamp"('now'::text)
  rating                 | double precision         | default 0.5


Thanks Tom.  I at my wit's end here.

/kurt


Tom Lane wrote:
> Kurt Overberg <kurt@hotdogrecords.com> writes:
>
>>delete from xrefmembergroup where membergroupid = 2 ; select 1 as true;
>
>
>>insert into xrefmembergroup (membergroupid, memberid) select 2 as
>>membergroupid, member.id as memberid from member where  ((extract(year
>>from age(birthdate))) >= '17' ); select 1 as true;
>
>
>>...my memory usage goes nuts- allocates 20-30 Mb per time I run this.
>
>
> Postgres version?
>
> Sounds like a memory leak, but there's not enough info here to debug it.
> Which of these queries exactly is leaking memory?  If it's the
> INSERT/SELECT (as I suspect), what's the schema of the 'member' table?
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
>