On 01/11/2014 11:06 AM, Bruce Momjian wrote:
> On Wed, May 29, 2013 at 09:59:10PM -0400, Peter Eisentraut wrote:
>> I think these sort of entries don't make much sense:
>>
>> #wal_sender_timeout = 60s # in milliseconds; 0 disables
>>
>> I think we should remove units from the comments when it'
Bruce Momjian writes:
> On Wed, May 29, 2013 at 09:59:10PM -0400, Peter Eisentraut wrote:
>> I think these sort of entries don't make much sense:
>>
>> #wal_sender_timeout = 60s # in milliseconds; 0 disables
>>
>> I think we should remove units from the comments when it's clear from
>> the
On Wed, May 29, 2013 at 09:59:10PM -0400, Peter Eisentraut wrote:
> I think these sort of entries don't make much sense:
>
> #wal_sender_timeout = 60s # in milliseconds; 0 disables
>
> I think we should remove units from the comments when it's clear from
> the name or the default value that
On 05/30/2013 01:14 AM, Heikki Linnakangas wrote:
On 30.05.2013 10:52, Joshua D. Drake wrote:
On 05/30/2013 12:01 AM, Heikki Linnakangas wrote:
We could make it mandatory to specify the unit in the value. Ie. throw
an error on "wal_sender_timeout = 50":
ERROR: unit required for option "wal_
On 30.05.2013 10:52, Joshua D. Drake wrote:
On 05/30/2013 12:01 AM, Heikki Linnakangas wrote:
We could make it mandatory to specify the unit in the value. Ie. throw
an error on "wal_sender_timeout = 50":
ERROR: unit required for option "wal_sender_timeout"
HINT: Valid units for this parameter
On 05/30/2013 12:55 AM, Magnus Hagander wrote:
I like this idea with one addition. We should have a default unit for each.
For wal_sender_timeout seconds makes sense, but for checkpoint_timeout
minutes makes sense (for example).
This sounds like a good way to make things even more confusing.
On Thu, May 30, 2013 at 3:52 AM, Joshua D. Drake wrote:
>
> On 05/30/2013 12:01 AM, Heikki Linnakangas wrote:
>
>> We could make it mandatory to specify the unit in the value. Ie. throw
>> an error on "wal_sender_timeout = 50":
>>
>> ERROR: unit required for option "wal_sender_timeout"
>> HINT: V
On 05/30/2013 12:01 AM, Heikki Linnakangas wrote:
We could make it mandatory to specify the unit in the value. Ie. throw
an error on "wal_sender_timeout = 50":
ERROR: unit required for option "wal_sender_timeout"
HINT: Valid units for this parameter are "ms", "s", "min", "h", and "d".
Then y
On 30.05.2013 06:43, Bruce Momjian wrote:
On Wed, May 29, 2013 at 09:59:10PM -0400, Peter Eisentraut wrote:
I think these sort of entries don't make much sense:
#wal_sender_timeout = 60s # in milliseconds; 0 disables
I think we should remove units from the comments when it's clear from
th
On Wed, May 29, 2013 at 09:59:10PM -0400, Peter Eisentraut wrote:
> I think these sort of entries don't make much sense:
>
> #wal_sender_timeout = 60s # in milliseconds; 0 disables
>
> I think we should remove units from the comments when it's clear from
> the name or the default value that
I think these sort of entries don't make much sense:
#wal_sender_timeout = 60s # in milliseconds; 0 disables
I think we should remove units from the comments when it's clear from
the name or the default value that time units are accepted.
--
Sent via pgsql-hackers mailing list (pgsql-hac
Jim C. Nasby wrote:
> On Tue, Jul 25, 2006 at 08:48:34AM +0200, Albe Laurenz wrote:
> > Peter Eisentraut wrote:
> > > So assuming we allowed units in postgresql.conf, how would you
> > > report them with SHOW?
> > >
> > > 1. The way they were set (hard)
> > >
> > > 2. Without units (not user-friend
On Tue, Jul 25, 2006 at 08:48:34AM +0200, Albe Laurenz wrote:
> Peter Eisentraut wrote:
> > So assuming we allowed units in postgresql.conf, how would you report
> > them with SHOW?
> >
> > 1. The way they were set (hard)
> >
> > 2. Without units (not user-friendly)
> >
> > 3. Always in base un
Peter Eisentraut wrote:
> So assuming we allowed units in postgresql.conf, how would you report
> them with SHOW?
>
> 1. The way they were set (hard)
>
> 2. Without units (not user-friendly)
>
> 3. Always in base units (seconds or bytes)
>
> 4. The largest unit that gives an integer
>
> (4) s
On Mon, Jul 24, 2006 at 11:13:53PM +0200, Peter Eisentraut wrote:
> So assuming we allowed units in postgresql.conf, how would you report
> them with SHOW?
>
> 1. The way they were set (hard)
>
> 2. Without units (not user-friendly)
>
> 3. Always in base units (seconds or bytes)
>
> 4. The lar
So assuming we allowed units in postgresql.conf, how would you report
them with SHOW?
1. The way they were set (hard)
2. Without units (not user-friendly)
3. Always in base units (seconds or bytes)
4. The largest unit that gives an integer
(4) seems the most reasonable to me in terms of inter
On Thursday 20 July 2006 18:16, Ron Mayer wrote:
> Peter Eisentraut wrote:
> > I think it would be useful to allow units to be added to these settings,
> > for example...
> > shared_buffers = 512MB
> > which is a bit cumbersome to calculate right now (you'd need = 65536).
> >
> > I haven't thought
Gavin, Peter,
> I would imagine that Peter intends to handle backward compatibility by
> processing values without explicit units in the units assumed pre <8.2.
Aha, I misunderstood.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)
Time units is easy:
1h = 60min = 3600s = 360ms
We don't need anything larger than seconds at the moment.
Except for log_rotation_age perhaps?
-- Korry
On Thu, 20 Jul 2006, Josh Berkus wrote:
> Peter,
>
> > I don't understand how that is related. Or what a conversion utility
> > would be for that matter.
>
> Well, the main issue with changing the units of the PostgreSQL.conf file
> from a user perspective is that the numbers from you 8.0/8.1 con
Peter Eisentraut wrote:
I think it would be useful to allow units to be added to these settings, for
example...
shared_buffers = 512MB
which is a bit cumbersome to calculate right now (you'd need = 65536).
I haven't thought yet how to parse or implement this, but would people find
this useful?
Peter Eisentraut wrote:
Zdenek Kotala wrote:
Time units is easy:
1h = 60min = 3600s = 360ms
We don't need anything larger than seconds at the moment.
What kind of unit prefix will we use for memory?
PostgreSQL has always used 1 kB = 1024 B.
1) will be unit required?
No.
What will
Peter Eisentraut wrote:
One frequent source of confusion are the different units that the parameters
in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
Obviously, we can't change that without inconvenien
On Thu, Jul 20, 2006 at 01:49:36PM +0200, Peter Eisentraut wrote:
> One frequent source of confusion are the different units that the parameters
> in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
> bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
> Ob
Peter,
> I don't understand how that is related. Or what a conversion utility
> would be for that matter.
Well, the main issue with changing the units of the PostgreSQL.conf file
from a user perspective is that the numbers from you 8.0/8.1 conf file
would no longer work. A little conversion
Josh Berkus wrote:
> Well, the main issue with changing the units of the PostgreSQL.conf
> file from a user perspective is that the numbers from you 8.0/8.1
> conf file would no longer work.
No one is intending to do any such change.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Josh Berkus wrote:
> Well, it's on my TODO list for 8.2 to write a simple postgresql.conf
> conversion utility in Perl. If you wanted to make a change like
> that, it would make finishing that mandatory.
I don't understand how that is related. Or what a conversion utility
would be for that mat
Zdenek Kotala wrote:
> Time units is easy:
> 1h = 60min = 3600s = 360ms
We don't need anything larger than seconds at the moment.
> What kind of unit prefix will we use for memory?
PostgreSQL has always used 1 kB = 1024 B.
> 1) will be unit required?
No.
> What will be default unit for va
Peter,
One frequent source of confusion are the different units that the parameters
in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
Obviously, we can't change that without inconveniencing a lot of us
On Thursday 20 July 2006 05:04, Jonah H. Harris wrote:
> On 7/20/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> > I think it would be useful to allow units to be added to these settings,
> > for example
> >
> > shared_buffers = 1000kB
> > checkpoint_warning = 30s
> >
> > This would also allow
>
Peter Eisentraut wrote:
One frequent source of confusion are the different units that the parameters
in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
Obviously, we can't change that without inconvenien
On 7/20/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
One frequent source of confusion are the different units that the parameters
in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
Obviously, we can't ch
On Thu, 20 Jul 2006, Peter Eisentraut wrote:
> One frequent source of confusion are the different units that the parameters
> in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
> bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
> Obviously, we can't change
On 7/20/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
I think it would be useful to allow units to be added to these settings, for
example
shared_buffers = 1000kB
checkpoint_warning = 30s
This would also allow
shared_buffers = 512MB
which is a bit cumbersome to calculate right now (you'd ne
One frequent source of confusion are the different units that the parameters
in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
Obviously, we can't change that without inconveniencing a lot of users.
I t
35 matches
Mail list logo
