I have added this TODO item:
Rationalize the discrepancy between settings that use values in bytes
and SHOW that returns the object count
* http://archives.postgresql.org/pgsql-docs/2008-07/msg7.php
---
On Aug 12, 2008, at 2:43 PM, Greg Smith wrote:
On Tue, 12 Aug 2008, Bruce Momjian wrote:
There's already some changes needed in this area needed to
execute the
full GUC cleanup/wizard plan that's being worked on. The
pg_settings view
really should show the value both as the user input it and
On Tue, 12 Aug 2008, Bruce Momjian wrote:
There's already some changes needed in this area needed to execute the
full GUC cleanup/wizard plan that's being worked on. The pg_settings view
really should show the value both as the user input it and as it's stored
internally for cases like these, w
Greg Smith wrote:
> On Thu, 24 Jul 2008, Greg Sabino Mullane wrote:
>
> > Bite the bullet and start showing the buffer settings as a pure number of
> > bytes
> > everywhere, and get rid of the confusing '8kB' unit in pg_settings?
>
> There's already some changes needed in this area needed to exe
On Thu, 24 Jul 2008, Greg Sabino Mullane wrote:
Bite the bullet and start showing the buffer settings as a pure number of bytes
everywhere, and get rid of the confusing '8kB' unit in pg_settings?
There's already some changes needed in this area needed to execute the
full GUC cleanup/wizard pl
On Thu, 2008-07-24 at 17:54 +, Greg Sabino Mullane wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
> NotDashEscaped: You need GnuPG to verify this message
>
>
> >> shared_buffers is in disk block size, typically 8K
>
> > The table the OP is looking at (table 17.2 in the 8.3 doc
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
NotDashEscaped: You need GnuPG to verify this message
>> shared_buffers is in disk block size, typically 8K
> The table the OP is looking at (table 17.2 in the 8.3 docs) predates
> the ability to specify shared_buffers in KB or MB instead of
>
