From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jude Weaver <exec(at)shreve(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Maximum columns for optimum performance (fwd) |
Date: | 2000-02-17 01:38:38 |
Message-ID: | 5256.950751518@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> forwards:
> One of our tables have 476 columns and only 12 records or rows in it. We are
> coding in Java. When we compile and run against this table it is super slow.
> Is there a maximum number of columns past which performance suffers?
What exactly are you finding to be super slow? It's hard to tell from
this report whether the performance problem is in the backend or the
Java client interface (or even in your application code...)
While I can think of places that have loops over columns, I wouldn't
have thought that any of them are remarkably time-critical. It
probably depends on just what sort of query you are doing ... so a
specific example of a slow query would be helpful, along with the
details of the table declaration.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bitmead | 2000-02-17 02:34:48 | Re: [HACKERS] FYI: BNF for SQL93 and SQL-3 |
Previous Message | Hiroshi Inoue | 2000-02-17 00:42:24 | create database doesn't work well in MULTIBYTE mode |