Re: Fwd: postgresql performance question

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: 許耀彰 <kpm906(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Fwd: postgresql performance question
Date: 2018-02-12 17:55:37
Message-ID: 3f3e6ce4-96ac-5608-3aef-02ded0ccaa8e@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 02/11/2018 04:15 PM, 許耀彰 wrote:
> Dear Support Team, 
> I create a table by command as listed as below:
> *CREATE TABLE public.log2*
> *(*
> *        d3 text COLLATE pg_catalog."default"*
> *)*
> *WITH (*
> *
> *
> *    OIDS = FALSE*
> *
> *
> *)*
> *
> *
> *TABLESPACE pg_default;*
>
> And then use command as listed as below to import data to log2 table
>
> *COPY log2 FROM '/home/anderson/0107.csv' CSV HEADER;*
>
> My purpose is to import log information to log2 table to analysis, but I
> found one situation : for example , I have 166856 records in log2 table,
> when I use select command to list data , it spent a lot time, can we
> adjust the situation ? 
> *select * from log2 *
> Thanks for your kindly assistance.

Sorry for being annoying, but this mailing list is for bug reports, and
your post is clearly not one. Please, send it to pgsql-performance, more
people are watching that list and you're more likely to get help.

Furthermore, I strongly recommend reading this:

https://wiki.postgresql.org/wiki/Slow_Query_Questions

It may actually have answer to your question, and in case it does not it
lists things you need to include in your post. For example query plan or
information about the hardware/system would be very helpful.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Gierth 2018-02-12 19:31:00 Re: BUG #15060: Row in table not found when using pg function in an expression
Previous Message PG Bug reporting form 2018-02-12 17:35:56 BUG #15061: Cannot use TEMP TABLE ON COMMIT DROP in extension