Gavin Sherry wrote:
On Wed, 18 Aug 2004, Gaetano Mendola wrote:
Gavin Sherry wrote:
On Wed, 18 Aug 2004, Gaetano Mendola wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
now that we have the tablespace support don't you think that
each tablespace needs his own costs instead of a syste
The first is to add a parameter to CREATE TABLESPACE and ALTER TABLESPACE
called RANDOMPAGECOST (or something like that) which allows users to set
the random page cost for a given tablespace. I'm undecided as to whether
they should be able to set the sequential scan cost. That seems
reasonable too
On Wed, 18 Aug 2004, Gaetano Mendola wrote:
> Gavin Sherry wrote:
>
> > On Wed, 18 Aug 2004, Gaetano Mendola wrote:
> >>-BEGIN PGP SIGNED MESSAGE-
> >>Hash: SHA1
> >>
> >>Hi all,
> >>now that we have the tablespace support don't you think that
> >>each tablespace needs his own costs instea
Gavin Sherry wrote:
On Wed, 18 Aug 2004, Gaetano Mendola wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
now that we have the tablespace support don't you think that
each tablespace needs his own costs instead of a system wide
one ?
I searched in the archives and on the TODO list witho
On Wed, 18 Aug 2004, Gaetano Mendola wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
> now that we have the tablespace support don't you think that
> each tablespace needs his own costs instead of a system wide
> one ?
>
> I searched in the archives and on the TODO list withou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
now that we have the tablespace support don't you think that
each tablespace needs his own costs instead of a system wide
one ?
I searched in the archives and on the TODO list without success.
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE
