Re: Fwd: postgresql performance question

From: Pavan Teja <pavan(dot)postgresdba(at)gmail(dot)com>
To: 許耀彰 <kpm906(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Fwd: postgresql performance question
Date: 2018-02-11 16:14:20
Message-ID: CACh9nsZUA+4hwpXgijkbquQ+tsSPCv6JKnrP-p_wVV_n3B+4Sw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

You can filter by using error_severity condition in the where Clause like:
Select * from log2 where error_severity ='error';

Regards,
Pavan

On Feb 11, 2018 9:31 PM, "許耀彰" <kpm906(at)gmail(dot)com> 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.
> Additional information: The attachment is log format
> Best Regards, Anderson Hsu
>
>
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Mark Scheffer 2018-02-12 07:38:33 Re: BUG #15026: Deadlock using GIST index
Previous Message 許耀彰 2018-02-11 15:15:24 Fwd: postgresql performance question