Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TSuqz-0007d0-D3 for pgsql-performance@postgresql.org; Mon, 29 Oct 2012 19:18:29 +0000 Received: from nm34-vm6.bullet.mail.ne1.yahoo.com ([98.138.229.86]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TSuqs-0007Wb-4D for pgsql-performance@postgresql.org; Mon, 29 Oct 2012 19:18:29 +0000 Received: from [98.138.90.56] by nm34.bullet.mail.ne1.yahoo.com with NNFMP; 29 Oct 2012 19:18:20 -0000 Received: from [98.138.89.162] by tm9.bullet.mail.ne1.yahoo.com with NNFMP; 29 Oct 2012 19:18:20 -0000 Received: from [127.0.0.1] by omp1018.mail.ne1.yahoo.com with NNFMP; 29 Oct 2012 19:18:20 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 226017.50667.bm@omp1018.mail.ne1.yahoo.com Received: (qmail 74122 invoked by uid 60001); 29 Oct 2012 19:18:20 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1351538300; bh=yysI3LM/5h5X8hzXH8e3MEKzv9zu5IBLpwn8T9s1BKI=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=j81B+udx5yZQTWWm1x2jGhmBLy3L4rr76Dim1l1eqGhRlCaltkaxZop9vfO5hF2hVxNmqb2psWxoQF8x3qkR+WDjnIZGz9IcSTsOQZXb24+2DZfYa5zDzGCcTfW4H/ily7/3Vy4EHb8qtI059aPTrqruOQv6s0W/7g7na6m5EiI= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=Xn1wImK4wNcvpm8gEF+G/Av8YCIoPeI+pFXN0345fq56ZDtaAXpHWzT6XCR8/YAH1XeC3zCvuNWLj3mw8Cft42Qh4aalAIfjzvAT7HoWVnMtzo9NTe3Qv/+CF8Hidvw3BGYWRyfne1SpNieiIywpYnXf5YOobmHZPVcqW8loSFk=; X-YMail-OSG: TDG2PKUVM1l8iPeqVRQ1kubLttt.YF9O_xoTlKt5EnRXbBE dxOH_BI6EJDT73TT2jdtVgIBoslzgeReaTbaejatZTU_GKpH6zs9OD9gOk5V j34Qzsttuq2h0Gvj5eZR4ZY0gycV5WO1OxsPbjsMFUt8vGeOQwXguN8viTWe TGNZQ5Uqa9rtpudHD_IngpJY2qKy318MgcY13sOGUtDOVSn5hNnRHFZkFbaw q8MifKORPX3NgL0pSR.vxxWve.VDREtUlE1pay2A6TpYZDR9kbS6Uj_o6FJY GlJi9eiwKNtrmDDehXbsi_O2M3s_gowbZE6rJPsS.d5svFA9Q7UN41EHgY98 GIZ04rfZH4dhs7a0uKoomsJ5Q2OrJQa69EFDNzuqs.7qUDQq4UrbpbIgsSbW qLTlR1mS3aYLO2U1jyC.4reSjGi2GSTgHiv1p2yIcfic4Qn63Kb9T1Fdgnh3 qxHQqQhR5KAa.4Q97VBRgjJkLfDnoxJj.PczwkrTeuOrrC4i2PWEVdStc2.I GHXiI_U8sXbMKEKc06InD3wNhXCBDsYI2rRAfryBlDPTracFwKekNmwCJqBU nKI7IIpEmf.LnTGaiFlrEgTNKO_oicYbCKSEz4ewv0mZVvk1VJpfP8DD_0va Zdltq Received: from [93.200.165.78] by web122203.mail.ne1.yahoo.com via HTTP; Mon, 29 Oct 2012 12:18:19 PDT X-Rocket-MIMEInfo: 001.001, RGlkIHlvdSB0cnkgdG8gYWRkIGFuIGluZGV4IG9uIGZpbGVzeXN0ZW1faWQgCgoKCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KIEZyb206ICJXb29sY29jaywgU2VhbiIgPFNlYW4uV29vbGNvY2tAZW1jLmNvbT4KVG86ICJwZ3NxbC1wZXJmb3JtYW5jZUBwb3N0Z3Jlc3FsLm9yZyIgPHBnc3FsLXBlcmZvcm1hbmNlQHBvc3RncmVzcWwub3JnPiAKU2VudDogTW9uZGF5LCBPY3RvYmVyIDI5LCAyMDEyIDY6NDEgUE0KU3ViamVjdDogW1BFUkZPUk1dIFJlcXVlc3QgZm9yIGhlbHAgd2l0aCBzbG8BMAEBAQE- X-Mailer: YahooMailWebService/0.8.123.460 References: <998490E92A198A48BE60F3A9C44CA3F1010A7DCF3901@MX40A.corp.emc.com> Message-ID: <1351538299.55595.YahooMailNeo@web122203.mail.ne1.yahoo.com> Date: Mon, 29 Oct 2012 12:18:19 -0700 (PDT) From: salah jubeh Reply-To: salah jubeh Subject: Re: Request for help with slow query To: "Woolcock, Sean" , "pgsql-performance@postgresql.org" In-Reply-To: <998490E92A198A48BE60F3A9C44CA3F1010A7DCF3901@MX40A.corp.emc.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="1629896970-44008646-1351538299=:55595" X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201210/353 X-Sequence-Number: 48312 --1629896970-44008646-1351538299=:55595 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Did you try to add an index on filesystem_id =0A=0A=0A=0A=0A=0A____________= ____________________=0A From: "Woolcock, Sean" =0ATo= : "pgsql-performance@postgresql.org" =0A= Sent: Monday, October 29, 2012 6:41 PM=0ASubject: [PERFORM] Request for hel= p with slow query=0A =0AHi, thanks for any help. I've tried to be thorough,= but let me know if I should=0Aprovide more information.=0A=0AA description= of what you are trying to achieve and what results you expect:=0A=A0 =A0 I= have a large (3 million row) table called "tape" that represents files,=0A= =A0 =A0 which I join to a small (100 row) table called "filesystem" that re= presents=0A=A0 =A0 filesystems.=A0 I have a web interface that allows you t= o sort by a number of=0A=A0 =A0 fields in the tape table and view the resul= ts 100 at a time (using LIMIT=0A=A0 =A0 and OFFSET).=0A=0A=A0 =A0 The data = only changes hourly and I do a "vacuum analyze" after all changes.=0A=0A=A0= =A0 The tables are defined as:=0A=0A=A0 =A0 =A0 =A0 create table filesyste= m (=0A=A0 =A0 =A0 =A0 =A0 =A0 id=A0 =A0 =A0 =A0 =A0 serial primary key,=0A= =A0 =A0 =A0 =A0 =A0 =A0 host=A0 =A0 =A0 =A0 varchar(256),=0A=A0 =A0 =A0 = =A0 =A0 =A0 storage_path varchar(2048) not null check (storage_path !=3D ''= ),=0A=A0 =A0 =A0 =A0 =A0 =A0 mounted_on=A0 varchar(2048) not null check (m= ounted_on !=3D ''),=0A=A0 =A0 =A0 =A0 =A0 =A0 constraint=A0 unique_fs uniq= ue(host, storage_path)=0A=A0 =A0 =A0 =A0 );=0A=A0 =A0 =A0 =A0 create table = tape (=0A=A0 =A0 =A0 =A0 =A0 =A0 id=A0 =A0 =A0 =A0 =A0 =A0 =A0 serial prim= ary key,=0A=A0 =A0 =A0 =A0 =A0 =A0 volser=A0 =A0 =A0 =A0 =A0 char(255) not= null check (volser !=3D ''),=0A=A0 =A0 =A0 =A0 =A0 =A0 path=A0 =A0 =A0 =A0= =A0 =A0 varchar(2048)=A0 not null check (path !=3D ''),=0A=A0 =A0 =A0 = =A0 =A0 =A0 scratched=A0 =A0 =A0 =A0 boolean=A0 =A0 =A0 =A0 not null defau= lt FALSE,=0A=A0 =A0 =A0 =A0 =A0 =A0 last_write_date=A0 timestamp=A0 =A0 =A0= not null default current_timestamp,=0A=A0 =A0 =A0 =A0 =A0 =A0 last_access= _date timestamp=A0 =A0 =A0 not null default current_timestamp,=0A=A0 =A0 = =A0 =A0 =A0 =A0 filesystem_id=A0 =A0 integer references filesystem not null= ,=0A=A0 =A0 =A0 =A0 =A0 =A0 size=A0 =A0 =A0 =A0 =A0 =A0 bigint not null ch= eck (size >=3D 0),=0A=A0 =A0 =A0 =A0 =A0 =A0 worm_status=A0 =A0 =A0 char,= =0A=A0 =A0 =A0 =A0 =A0 =A0 encryption=A0 =A0 =A0 char,=0A=A0 =A0 =A0 =A0 = =A0 =A0 job_name=A0 =A0 =A0 =A0 char(8),=0A=A0 =A0 =A0 =A0 =A0 =A0 job_ste= p=A0 =A0 =A0 =A0 char(8),=0A=A0 =A0 =A0 =A0 =A0 =A0 dsname=A0 =A0 =A0 =A0 = =A0 char(17),=0A=A0 =A0 =A0 =A0 =A0 =A0 recfm=A0 =A0 =A0 =A0 =A0 =A0 char(= 3),=0A=A0 =A0 =A0 =A0 =A0 =A0 block_size=A0 =A0 =A0 int,=0A=A0 =A0 =A0 =A0= =A0 =A0 lrecl=A0 =A0 =A0 =A0 =A0 =A0 int,=0A=A0 =A0 =A0 =A0 =A0 =A0 constr= aint filesystem_already_has_that_volser unique(filesystem_id, volser)=0A=A0= =A0 =A0 =A0 );=0A=0A=A0 =A0 An example query that's running slowly for me = is:=0A=0A=A0 =A0 =A0 =A0 select tape.volser,=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 = tape.path,=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 tape.scratched,=0A=A0 =A0 =A0 = =A0 =A0 =A0 =A0 tape.size,=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 extract(epoch fr= om tape.last_write_date) as last_write_date,=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 = extract(epoch from tape.last_access_date) as last_access_date=0A=A0 =A0 = =A0 =A0 =A0 =A0 from tape=0A=A0 =A0 =A0 =A0 =A0 =A0 inner join filesystem= =0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 on (tape.filesystem_id =3D filesystem.id= )=0A=A0 =A0 =A0 =A0 =A0 =A0 order by last_write_date desc=0A=A0 =A0 =A0 =A0= =A0 =A0 limit 100=0A=A0 =A0 =A0 =A0 =A0 =A0 offset 100;=0A=0A=A0 =A0 On Po= stgres 8.1.17 this takes about 60 seconds. I would like it to be faster.=0A= =0A=A0 =A0 Here's the explain output:=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 QUERY PLAN=0A=A0 =A0 =A0 =A0 ------------------= ---------------------------------------------------------------------------= ------------------------------------------=0A=A0 =A0 =A0 =A0 Limit=A0 (cost= =3D3226201.13..3226201.38 rows=3D100 width=3D308) (actual time=3D66311.929.= .66312.053 rows=3D100 loops=3D1)=0A=A0 =A0 =A0 =A0 ->=A0 Sort=A0 (cost=3D32= 26200.88..3234250.28 rows=3D3219757 width=3D308) (actual time=3D66311.826..= 66311.965 rows=3D200 loops=3D1)=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Sort Key:= date_part('epoch'::text, tape.last_write_date)=0A=A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 ->=A0 Hash Join=A0 (cost=3D3.26..242948.97 rows=3D3219757 width=3D3= 08) (actual time=3D3.165..31680.830 rows=3D3219757 loops=3D1)=0A=A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 Hash Cond: ("outer".filesystem_id =3D "inner".= id)=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ->=A0 Seq Scan on tape=A0 (co= st=3D0.00..178550.57 rows=3D3219757 width=3D312) (actual time=3D2.824..1817= 5.863 rows=3D3219757 loops=3D1)=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -= >=A0 Hash=A0 (cost=3D3.01..3.01 rows=3D101 width=3D4) (actual time=3D0.204.= .0.204 rows=3D101 loops=3D1)=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 ->=A0 Seq Scan on filesystem=A0 (cost=3D0.00..3.01 rows=3D101 w= idth=3D4) (actual time=3D0.004..0.116 rows=3D101 loops=3D1)=0A=A0 =A0 =A0 = =A0 Total runtime: 66553.643 ms=0A=0A=A0 =A0 Here's a depesz link with that= output: http://explain.depesz.com/s/AUR=0A=0A=0AThings I've tried:=0A=0A= =A0 =A0 1. I added an index on last_write_date with:=0A=0A=A0 =A0 =A0 =A0 = =A0 =A0 create index tape_last_write_date_idx on tape(last_write_date);=0A= =0A=A0 =A0 =A0 and there was no improvement in query time.=0A=0A=A0 =A0 2.= I bumped:=0A=A0 =A0 =A0 =A0 =A0 =A0 effective_cache_size to 1/2 system RA= M (1GB)=0A=A0 =A0 =A0 =A0 =A0 =A0 shared_buffers to 1/4 system RAM (512MB)= =0A=A0 =A0 =A0 =A0 =A0 =A0 work_mem to 10MB=0A=A0 =A0 =A0 and there was n= o improvement in query time.=0A=0A=A0 =A0 3. I ran the query against the sa= me data in Postgres 9.1.6 rather than 8.1.17=0A=A0 =A0 =A0 using the same = hardware and it was about 5 times faster (nice work,=0A=A0 =A0 =A0 whoever= did that!).=A0 Unfortunately upgrading is not an option, so this=0A=A0 =A0= =A0 is more of an anecdote. I would think the query could go much faster= =0A=A0 =A0 =A0 in either environment with some optimization.=0A=0A=0A=0ATh= e EXACT PostgreSQL version you are running:=0A=A0 =A0 PostgreSQL 8.1.17 on = i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.1.2 20070115 (SUSE Linux)=0A= =0AHow you installed PostgreSQL:=0A=A0 =A0 Standard SuSE SLES 10-SP3 RPMs:= =0A=A0 =A0 =A0 =A0 postgresql-devel-8.1.17-0.3=0A=A0 =A0 =A0 =A0 postgresql= -pl-8.1.17-0.4=0A=A0 =A0 =A0 =A0 postgresql-libs-8.1.17-0.3=0A=A0 =A0 =A0 = =A0 postgresql-8.1.17-0.3=0A=A0 =A0 =A0 =A0 postgresql-server-8.1.17-0.3=0A= =A0 =A0 =A0 =A0 postgresql-contrib-8.1.17-0.3=0A=0AChanges made to the sett= ings in the postgresql.conf file:=0A=A0 =A0 Only the memory changes mention= ed above.=0A=0AOperating system and version:=0A=A0 =A0 Linux acp1 2.6.16.60= -0.54.5-default #1 Fri Sep 4 01:28:03 UTC 2009 i686 i686 i386 GNU/Linux=0A= =0A=A0 =A0 SLES 10-SP3=0A=0AWhat program you're using to connect to Postgre= SQL:=0A=A0 =A0 Perl DBI=0A=A0 =A0 Perl v5.8.8=0A=0AWhat version of the ODBC= /JDBC/ADO/etc driver you're using, if any:=0A=A0 =A0 perl-DBD-Pg 1.43=0A=0A= If you're using a connection pool, load balancer or application server, whi= ch one you're using and its version:=0A=A0 =A0 None.=0A=0AIs there anything= remotely unusual in the PostgreSQL server logs?=0A=A0 =A0 No, they're empt= y.=0A=0A=0ACPU manufacturer and model:=0A=A0 =A0 Intel Celeron CPU 440 @ 2.= 00GHz=0A=0AAmount and size of RAM installed:=0A=A0 =A0 2GB RAM=0A=0AStorage= details (important for performance and corruption questions):=0A=0A=A0 =A0= Do you use a RAID controller?=0A=A0 =A0 =A0 =A0 No.=0A=A0 =A0 How many har= d disks are connected to the system and what types are they?=0A=A0 =A0 =A0 = =A0 We use a single Hitachi HDT72102 SATA drive (250GB) 7200 RPM.=0A=A0 =A0= How are your disks arranged for storage?=0A=A0 =A0 =A0 =A0 Postgres lives = on the same 100GB ext3 partition as the OS.=0A=0A=0AThanks,=0ASean=0A=0A=0A= -- =0ASent via pgsql-performance mailing list (pgsql-performance@postgresql= .org)=0ATo make changes to your subscription:=0Ahttp://www.postgresql.org/m= ailpref/pgsql-performance --1629896970-44008646-1351538299=:55595 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Did you try to add an index on= filesystem_id



From: = "Woolcock, Sean" <Sean.Woolcock@emc.com>
To: "pgsql-performance@postgresql.org" <pgsql-p= erformance@postgresql.org>
Se= nt: Monday, October 29, 2012 6:41 PM
Subject: [PERFORM] Request for help with slow que= ry

=0AHi, thanks for any help. I've tried to be thor= ough, but let me know if I should
provide more information.

A des= cription of what you are trying to achieve and what results you expect:
=     I have a large (3 million row) table called "tape" that repre= sents files,
    which I join to a small (100 row) table calle= d "filesystem" that represents
    filesystems.  I have a= web interface that allows you to sort by a number of
    fiel= ds in the tape table and view the results 100 at a time (using LIMIT
&nb= sp;   and OFFSET).

    The data only changes hourly a= nd I do a "vacuum analyze" after all changes.

    The tabl= es are defined as:

        create table filesyst= em (
            id      &n= bsp;   serial primary key,
          &nbs= p; host        varchar(256),
            = storage_path varchar(2048) not null check (storage_path !=3D ''),
 =           mounted_on  varchar(2048) not nul= l check (mounted_on !=3D ''),
            = constraint  unique_fs unique(host, storage_path)
    &nb= sp;   );
        create table tape (
  =           id          &nb= sp;   serial primary key,
           = ; volser          char(255) not null check (volse= r !=3D ''),
            path    =         varchar(2048)  not null check (path !=3D= ''),
            scratched    &= nbsp;   boolean        not null default FALSE,
            last_write_date  = timestamp      not null default current_timestamp,
 = ;           last_access_date timestamp   = ;   not null default current_timestamp,
       = ;     filesystem_id    integer references filesystem no= t null,
            size    &nbs= p;       bigint not null check (size >=3D 0),
  =           worm_status      char,            encryption      = char,
            job_name    &n= bsp;   char(8),
            job_step=         char(8),
         =   dsname          char(17),
            recfm         =   char(3),
            block_size&nb= sp;     int,
            lrecl&= nbsp;           int,
       = ;     constraint filesystem_already_has_that_volser unique(filesy= stem_id, volser)
        );

    An = example query that's running slowly for me is:

      =   select tape.volser,
            &nb= sp; tape.path,
              tape.s= cratched,
              tape.size,              extract(epoch from tape= .last_write_date) as last_write_date,
         =     extract(epoch from tape.last_access_date) as last_access_date
            from tape            inner join filesystem
  =               on (tape.filesystem_id =3D= filesystem.id)
=             order by last_write_date desc
=             limit 100
     =       offset 100;

    On Postgres 8.1.17 t= his takes about 60 seconds. I would like it to be faster.

  &nb= sp; Here's the explain output:
           =                     &nbs= p;                     &n= bsp;             QUERY PLAN
    =     --------------------------------------------------------------------------= -------------------------------------------------------------
  &nb= sp;     Limit  (cost=3D3226201.13..3226201.38 rows=3D100 wid= th=3D308) (actual time=3D66311.929..66312.053 rows=3D100 loops=3D1)
&nbs= p;       ->  Sort  (cost=3D3226200.88..3234250.= 28 rows=3D3219757 width=3D308) (actual time=3D66311.826..66311.965 rows=3D2= 00 loops=3D1)
                So= rt Key: date_part('epoch'::text, tape.last_write_date)
    &nb= sp;           ->  Hash Join  (cost=3D= 3.26..242948.97 rows=3D3219757 width=3D308) (actual time=3D3.165..31680.830= rows=3D3219757 loops=3D1)
            &nb= sp;       Hash Cond: ("outer".filesystem_id =3D "inner".id)<= br>                    -&= gt;  Seq Scan on tape  (cost=3D0.00..178550.57 rows=3D3219757 width=3D312) (actual tim= e=3D2.824..18175.863 rows=3D3219757 loops=3D1)
      &nbs= p;             ->  Hash  (cost= =3D3.01..3.01 rows=3D101 width=3D4) (actual time=3D0.204..0.204 rows=3D101 = loops=3D1)
                 = ;           ->  Seq Scan on filesystem&nbs= p; (cost=3D0.00..3.01 rows=3D101 width=3D4) (actual time=3D0.004..0.116 row= s=3D101 loops=3D1)
        Total runtime: 66553.643 = ms

    Here's a depesz link with that output: http://expla= in.depesz.com/s/AUR


Things I've tried:

    1. I= added an index on last_write_date with:

       =     create index tape_last_write_date_idx on tape(last_write_dat= e);

      and there was no improvement in query time= .

    2. I bumped:
            effective_cache_size= to 1/2 system RAM (1GB)
            shar= ed_buffers to 1/4 system RAM (512MB)
          =   work_mem to 10MB
      and there was no improvem= ent in query time.

    3. I ran the query against the same= data in Postgres 9.1.6 rather than 8.1.17
      using t= he same hardware and it was about 5 times faster (nice work,
  &nbs= p;   whoever did that!).  Unfortunately upgrading is not an opti= on, so this
      is more of an anecdote. I would think = the query could go much faster
      in either environme= nt with some optimization.



The EXACT PostgreSQL version you = are running:
    PostgreSQL 8.1.17 on i686-pc-linux-gnu, compi= led by GCC gcc (GCC) 4.1.2 20070115 (SUSE Linux)

How you installed PostgreSQL:
    Standard SuSE SLES 10-SP3 RPMs:
=         postgresql-devel-8.1.17-0.3
    &n= bsp;   postgresql-pl-8.1.17-0.4
        postgre= sql-libs-8.1.17-0.3
        postgresql-8.1.17-0.3        postgresql-server-8.1.17-0.3
    =     postgresql-contrib-8.1.17-0.3

Changes made to the sett= ings in the postgresql.conf file:
    Only the memory changes = mentioned above.

Operating system and version:
    Linu= x acp1 2.6.16.60-0.54.5-default #1 Fri Sep 4 01:28:03 UTC 2009 i686 i686 i3= 86 GNU/Linux

    SLES 10-SP3

What program you're us= ing to connect to PostgreSQL:
    Perl DBI
    Pe= rl v5.8.8

What version of the ODBC/JDBC/ADO/etc driver you're using,= if any:
    perl-DBD-Pg 1.43

If you're using a connection pool, load balancer or application server, which one you're usi= ng and its version:
    None.

Is there anything remotel= y unusual in the PostgreSQL server logs?
    No, they're empty= .


CPU manufacturer and model:
    Intel Celeron CPU= 440 @ 2.00GHz

Amount and size of RAM installed:
    2G= B RAM

Storage details (important for performance and corruption ques= tions):

    Do you use a RAID controller?
   =     No.
    How many hard disks are connected to th= e system and what types are they?
        We use a s= ingle Hitachi HDT72102 SATA drive (250GB) 7200 RPM.
    How ar= e your disks arranged for storage?
        Postgres = lives on the same 100GB ext3 partition as the OS.


Thanks,
Sea= n


--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make= changes to your subscription:
http://www.postgresql.org/mailpre= f/pgsql-performance


--1629896970-44008646-1351538299=:55595--