Quoting Tom Lane <[EMAIL PROTECTED]>:
> Javier Carlos <[EMAIL PROTECTED]> writes:
> >When I make a SELECT with many tables (more than 12), postgresql eats
> all my
> > %CPU and I've waited more than 1 hour and stays the same. The weird thing
> is
> > that with 10 tables the same select with th
Quoting Stephan Szabo <[EMAIL PROTECTED]>:
>
> On Mon, 24 Nov 2003, Javier Carlos wrote:
>
> > Quoting Stephan Szabo <[EMAIL PROTECTED]>:
> >
> > >
> > > On Mon, 24 Nov 2003, Javier Carlos wrote:
> > >
> > > >
> > > > Please enter a FULL description of your problem:
> > > > -
Javier Carlos <[EMAIL PROTECTED]> writes:
>When I make a SELECT with many tables (more than 12), postgresql eats all my
> %CPU and I've waited more than 1 hour and stays the same. The weird thing is
> that with 10 tables the same select with the same joins only takes about 5
> seconds. First I
Quoting Stephan Szabo <[EMAIL PROTECTED]>:
>
> On Mon, 24 Nov 2003, Javier Carlos wrote:
>
> >
> > Please enter a FULL description of your problem:
> > -
> >When I make a SELECT with many tables (more than 12), postgresql eats
> all my
> > %CPU
On Mon, 24 Nov 2003, Javier Carlos wrote:
> Quoting Stephan Szabo <[EMAIL PROTECTED]>:
>
> >
> > On Mon, 24 Nov 2003, Javier Carlos wrote:
> >
> > >
> > > Please enter a FULL description of your problem:
> > > -
> > >When I make a SELECT with ma
On Mon, 24 Nov 2003, Javier Carlos wrote:
>
> Please enter a FULL description of your problem:
> -
>When I make a SELECT with many tables (more than 12), postgresql eats all my
> %CPU and I've waited more than 1 hour and stays the same. The weir
POSTGRESQL BUG REPORT TEMPLATE
Your name: F. Javier Carlos Rivera
Your email address :
