| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Table with large number of int columns, very slow COPY FROM |
| Date: | 2017-12-08 07:20:40 |
| Message-ID: | 817fe5f2-c15e-4369-15ce-1e26f74bbbca@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On 08.12.2017 05:21, Alex Tokarev wrote:
> I have made a minimally reproducible test case consisting of a table
> with 848 columns
Such a high number of columns is maybe a sign of a wrong table /
database design, why do you have such a lot of columns? How many indexes
do you have?
Regards, Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2017-12-08 07:22:53 | Re: proposal: alternative psql commands quit and exit |
| Previous Message | Rui Hai Jiang | 2017-12-08 06:39:26 | Is it possible and worthy to optimize scanRTEForColumn()? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2017-12-08 13:20:16 | Re: Learning EXPLAIN |
| Previous Message | Mark Kirkwood | 2017-12-08 04:51:08 | Re: Setting effective_io_concurrency in VM? |