OK, it's quite some time from when the original question was posted, but
now I have more data... see below.
On Thu, 2005-09-29 at 19:24, Jim C. Nasby wrote:
> On Tue, Sep 27, 2005 at 10:24:02AM +0200, Csaba Nagy wrote:
> > Hi all,
> >
> > I've recently asked a similar question, which received no
On Tue, Sep 27, 2005 at 03:09:43PM +0530, surabhi.ahuja wrote:
> is it some logging information that is being written into some file at the
> end of some transactions
> (each intsall is one transaction for me)
>
> the data directory is containing these folders..
>
> base/pg_clog/ pg_i
On Tue, Sep 27, 2005 at 10:24:02AM +0200, Csaba Nagy wrote:
> Hi all,
>
> I've recently asked a similar question, which received no useful answer
> yet, so I'll drop in too.
>
> In my case, the table I was inserting to was a quite big one already to
> start with (and analyzed so), so I was expect
Hi all,
I've recently asked a similar question, which received no useful answer
yet, so I'll drop in too.
In my case, the table I was inserting to was a quite big one already to
start with (and analyzed so), so I was expecting that it will not slow
down due to indexes, as they were quite big to s
On Mon, 2005-09-26 at 12:58, Jim C. Nasby wrote:
> On Mon, Sep 26, 2005 at 05:55:18PM +0530, surabhi.ahuja wrote:
> > i have seen that after insertion say (20 k rows) the insertion to tables
> > becomes slow..why is it?
>
> Most likely due to indexes.
>
> > is there any way in which u can stop t
On Mon, Sep 26, 2005 at 05:55:18PM +0530, surabhi.ahuja wrote:
> i have seen that after insertion say (20 k rows) the insertion to tables
> becomes slow..why is it?
Most likely due to indexes.
> is there any way in which u can stop the performance from degrading
If you're loading from scratch,
