Tom Lane wrote:
> [ redirecting to pgsql-docs ]
>
> Valentin Bogdanov writes:
> >> From: dx k9
> >> I'm trying to understand what the documentation means
> >> by bytes per increment, what is the increment supposed to
> >> be bytes, MB, or Kb.
>
> > shared_buffers is in disk block size, typicall
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
---
Bruce Momjian wrote:
> Tom Lane wrote:
> > [ redirecting to pgsql-docs ]
> >
> > Valentin Bogdanov writes:
> > >> From: dx k9
> > >> I'm trying to understand what the documentation means
> > >> by bytes per increment, what is the increment supposed to
> > >> be bytes, MB, or Kb.
> >
> > > share
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> > > [ redirecting to pgsql-docs ]
> > >
> > > Valentin Bogdanov writes:
> > > >> From: dx k9
> > > >> I'm trying to understand what the documentation means
> > > >> by bytes per increment, what is the increment supposed to
> > >
Bruce Momjian writes:
> Alvaro Herrera wrote:
>> I don't find it any clearer ... I think the missing clue is that if you
>> specify shared_buffers values in MB, you must divide the value by block
>> size.
> Well, the heading says "object" now so I thought it would suggest we are
> talking about o
Tom Lane wrote:
> Robert Treat writes:
> > We had a doc comment come in noting that the second paragraph seems to be
> > incorrect on
> > http://www.postgresql.org/docs/8.3/interactive/rules-triggers.html,
> > specifically the part that says "On the other hand, a trigger that is fired
> > on I
Tom Lane wrote:
> Bruce Momjian writes:
> > Alvaro Herrera wrote:
> >> I don't find it any clearer ... I think the missing clue is that if you
> >> specify shared_buffers values in MB, you must divide the value by block
> >> size.
>
> > Well, the heading says "object" now so I thought it would su
