Re: [PERFORM] full outer performance problem

Quoting Tom Lane <[EMAIL PROTECTED]>: > Kim Bisgaard <[EMAIL PROTECTED]> writes: > > W.r.t. your rewrite of the query, I get this "ERROR: could not devise a > > query plan for the given query" but no further details - I will try google > > Which PG version are you using again? That should be fix

Re: [PERFORM] full outer performance problem

Quoting Tom Lane <[EMAIL PROTECTED]>: > Kim Bisgaard <[EMAIL PROTECTED]> writes: > > SELECT station_id, timeobs,temp_grass, temp_dry_at_2m > > FROM temp_dry_at_2m a > > FULL OUTER JOIN temp_grass b > > USING (station_id, timeobs) > > WHERE station_id = 52981 > >

Re: [PERFORM] full outer performance problem

Kim Bisgaard <[EMAIL PROTECTED]> writes: > W.r.t. your rewrite of the query, I get this "ERROR: could not devise a > query plan for the given query" but no further details - I will try google Which PG version are you using again? That should be fixed in 7.4.3 and later.

Re: [PERFORM] full outer performance problem

Kim Bisgaard <[EMAIL PROTECTED]> writes: > SELECT station_id, timeobs,temp_grass, temp_dry_at_2m > FROM temp_dry_at_2m a > FULL OUTER JOIN temp_grass b > USING (station_id, timeobs) > WHERE station_id = 52981 > AND timeobs = '2004-1-1 0:0:0' > explain ana

Re: [PERFORM] full outer performance problem

Hi Bruno, Thanks for the moral support! I feel so too - but I am confident it will show up soon. W.r.t. your rewrite of the query, I get this "ERROR: could not devise a query plan for the given query" but no further details - I will try google Regards, Kim. Bruno Wolff III wrote: On Wed

Re: [PERFORM] full outer performance problem

On Wed, Jun 08, 2005 at 11:37:40 +0200, Kim Bisgaard <[EMAIL PROTECTED]> wrote: > Hi, > > I'm having problems with the query optimizer and FULL OUTER JOIN on > PostgreSQL 7.4. I cannot get it to use my indexes with full outer joins. > I might be naive, but I think that it should be possible? >

[PERFORM] full outer performance problem

Hi, I'm having problems with the query optimizer and FULL OUTER JOIN on PostgreSQL 7.4. I cannot get it to use my indexes with full outer joins. I might be naive, but I think that it should be possible? I have two BIG tables (virtually identical) with 3 NOT NULL columns Station_id, TimeObs,

Re: [PERFORM] full outer performance problem

Sorry for not listing the exact layout of temp_: obsdb=> \d temp_dry_at_2m   Table "public.temp_dry_at_2m" Column |    Type | Modifiers +-+---  obshist_id | integer | not nul

Re: [PERFORM] full outer performance problem

Hi, Look for my comments further down... John A Meinel wrote: Kim Bisgaard wrote: Hi, I'm having problems with the query optimizer and FULL OUTER JOIN on PostgreSQL 7.4. I cannot get it to use my indexes with full outer joins. I might be naive, but I think that it should be possible? I have two BIG

Re: [PERFORM] full outer performance problem

Kim Bisgaard <[EMAIL PROTECTED]> writes: > I have two BIG tables (virtually identical) with 3 NOT NULL columns > Station_id, TimeObs, Temp_, with indexes on (Station_id, TimeObs) > and valid ANALYSE (set statistics=100). I want to join the two tables > with a FULL OUTER JOIN. I'm confused.

Re: [PERFORM] full outer performance problem

Kim Bisgaard wrote: Hi, I'm having problems with the query optimizer and FULL OUTER JOIN on PostgreSQL 7.4. I cannot get it to use my indexes with full outer joins. I might be naive, but I think that it should be possible? I have two BIG tables (virtually identical) with 3 NOT NULL columns Station_

[PERFORM] full outer performance problem

Hi, I'm having problems with the query optimizer and FULL OUTER JOIN on PostgreSQL 7.4. I cannot get it to use my indexes with full outer joins. I might be naive, but I think that it should be possible? I have two BIG tables (virtually identical) with 3 NOT NULL columns Station_id, TimeObs, T