Fwd: Re: Weird trouble with select
От | erobles |
---|---|
Тема | Fwd: Re: Weird trouble with select |
Дата | |
Msg-id | 4C2A01C0.3090406@sensacd.com.mx обсуждение исходный текст |
Ответы |
Re: Fwd: Re: Weird trouble with select
|
Список | pgsql-general |
-------- Original Message -------- Subject: Re: [GENERAL] Weird trouble with select Date: Tue, 29 Jun 2010 09:13:14 -0500 From: erobles <erobles@sensacd.com.mx> Organization: SENSA Control Digital To: Joshua Tolley <eggyknap@gmail.com> On 06/29/2010 08:59 AM, Joshua Tolley wrote: > On Tue, Jun 29, 2010 at 08:44:35AM -0500, erobles wrote: > >> Hi! >> >> I have 3 pc's: >> pc 'A' with postgres 7.2 running >> pc 'B' and 'C' connected to 'A' >> > You should upgrade as quickly as possible. 7.2 is ancient. Even 8.1 will hit > end-of-life soon. > We are testing postgres 8.3.11 to detect any problem when we migrate from 7.2 :-) >> if i made the next query on 'B' or 'C' : "select * from detail with >> id=72"; takes too long time to return the data, near of 10 minutes >> more or less. >> if i made the next query on 'B' or 'C' : "select * from detail with >> id=71", or whatever value in id , the data are returned immediatly. >> >> if i made the next query on 'A' (postgres server): "select * from >> detail with id=72", the data are returned immediatly. >> > > I wonder if you're just hitting caching effects, and the different client > hosts are confusing the issue. > If you issue the query from one machine > multiple times, does it reliably take forever the first time, and go quickly > afterward? > no, doesn't. This only works fine with a pc diferent to 'B' or 'C' if the query is executed many times only on 'B' the query always fail for id=72 with another value works fine.
В списке pgsql-general по дате отправления: