Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
random_page_cost etc. per tablespace?
- From: Jens-Wolfhard Schicke <drahflow(at)gmx(dot)de>
- To: pgsql-performance(at)postgresql(dot)org
- Subject: random_page_cost etc. per tablespace?
- Date: Tue, 13 Nov 2007 11:24:42 +0100
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, how hard would it be to give users the ability to configure different random_page and seq_page costs per tablespace? Obviously this does not match with random_page_cost being a GUC variable but nonetheless I think it'd make a nice feature. I just came across this problem because I own a solid state disk but not all data is stored there. Regards, Jens-W. Schicke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHOXtqzhchXT4RR5ARArkkAKCxljEjRF0vXDJyyLBVTVhnxJ/idwCeOYiD ndXrD8ZFvh5XUmzz5nTZbiI= =871T -----END PGP SIGNATURE-----
- Prev by Date: Re: Need to run CLUSTER to keep performance
- Next by Date: Re: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
- Previous by thread: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
- Next by thread: Re: [HACKERS] 8.3beta1 testing on Solaris
- Indexes: