On Saturday May 6 2006 7:15 pm, Ed L. wrote:
> I'm watching a long, painfully slow 60GB load from pg_dump
> (8.1.2), and noticing it's jumping back and forth from
> different tables. I assume this is the index creation order
> showing up.
>
> Would it make more sense
I'm watching a long, painfully slow 60GB load from pg_dump
(8.1.2), and noticing it's jumping back and forth from different
tables. I assume this is the index creation order showing up.
Would it make more sense to have pg_dump dump indexes grouped by
the table? That way, if a table got loaded
On Tuesday February 24 2004 1:14, Kevin Brown wrote:
>
> One problem I've been running into is the merge join spilling to disk
> because sort_mem isn't big enough. The problem isn't that this is
> happening, it's that I think the planner is underestimating the impact
> that doing this will have on
On Monday February 23 2004 10:23, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > If I could say it the way I think for a simple example, it'd be
> > like this:
> >
> > delete from mytable
> > where posteddatetime < now()
A 7.3.4 question...
I want to "expire" some data after 90 days, but not delete too
much at once so as not to overwhelm a system with precariously
balanced disk I/O and on a table with millions of rows. If I
could say it the way I think for a simple example, it'd be
like this:
delete fr
