Re: share info between backends

Поиск
Список
Период
Сортировка
От Jaime Casanova
Тема Re: share info between backends
Дата
Msg-id c2d9e70e0701111819p1e719a19j6049114942583f2d@mail.gmail.com
обсуждение исходный текст
Ответ на Re: share info between backends  ("Andrew Dunstan" <andrew@dunslane.net>)
Ответы Re: share info between backends  ("Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>)
Список pgsql-hackers
On 1/11/07, Andrew Dunstan <andrew@dunslane.net> wrote:
> Jaime Casanova wrote:
> >
> > i'm trying to fix a problem related to the patch Albert sent in
> > october (Tablespace for temporary objects and sort files)
> > http://archives.postgresql.org/pgsql-patches/2006-10/msg00141.php
> > http://archives.postgresql.org/pgsql-patches/2007-01/msg00063.php
> >
> > after reviewing this i notice this will not use different tablespaces
> > in the case of having various connections all with just one temp
> > table:
> > http://archives.postgresql.org/pgsql-patches/2007-01/msg00188.php
> >
> > what i'm trying to do it is share what's the next_temp_tablespace to
> > use...
> > the other way to do this is as you say using tables, but i don't think
> > this is a good idea in this case...
> >
> > comments?
> >
>
> Why not make it probabilistic by using, say, MyProcPid % n where n is the
> number of tablespaces? Then you don't need anything shared.
>

mmm... is not great to try to kill flies with tanks? ;)
thanks for the idea, i will try it

-- 
regards,
Jaime Casanova

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."                                      Richard Cook


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Christopher Kings-Lynne"
Дата:
Сообщение: Re: PANIC: block 463 unfound during REDO after out of
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [PERFORM] unusual performance for vac following 8.2upgrade