From: | Nick Raj <nickrajjain(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Logfile |
Date: | 2011-05-23 04:56:44 |
Message-ID: | BANLkTimn+iis5SEx6gbwui5Ow731Rkbuag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
sorry, actually becuase of one printf statement(i have added) because of
that, these has been occured. My mistake
On Mon, May 23, 2011 at 9:06 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sun, May 22, 2011 at 6:42 AM, Nick Raj <nickrajjain(at)gmail(dot)com> wrote:
> > I am using contrib/cube code. I am building GIST index on cube data type
> > then it leads to a very large size of log file (nearly 220 MB for only
> 12k
> > records).
> > While creating index on geometry field with gist gives 1KB size of log
> file
> > for 17 lakh records.
> >
> > Can someone please tell me how to stop postgres to logged so much data in
> > case of cube?
>
> Well, I don't have a clue why it would be writing that many log
> messages. Maybe you should look in the log file and see what those
> messages are specifically... with a few more details, someone might be
> able to help you out.
>
> Also, this question would be better directed to pgsql-general or
> pgsql-admin.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
From | Date | Subject | |
---|---|---|---|
Next Message | nil nil | 2011-05-23 04:59:04 | Fw: Help required regarding patch development |
Previous Message | Tom Lane | 2011-05-23 03:49:15 | Re: 9.1 support for hashing arrays |