gregs1104 / pgtune Goto Github PK

"-M or --memory: Use this parameter to specify total system memory. If not specified, pgtune will attempt to detect memory size."

Do I specify it in bytes?

Is the 9.1 data file safe to use for configuring a 9.2? The diff between 9.0 and 9.1 are substantial so probably not?

Not a huge issue but it tripped me up for a bit. pgtune commented out the "listen_on" addresses field, which I had set to "*" to allow external requests.

BTW pgtune is really awesome.

In pg_tune there is an option to set the database type:
-T or --type : Specifies database type. Valid options are: DW, OLTP, Web, Mixed, Desktop

It would be helpful to provide more detailed explanation of the database types and what a user should consider when choosing one option over the others.

Thank you for all your hard work on pg_tune.

I think this sentence under "Source installation" is missing a chunk:

Note that you will need the multiple

I just ran pgtune. It suggested an adjustment to checkpoint_segments. However, according to https://www.postgresql.org/docs/9.6/static/release-9-5.html, checkpoint_segments is no longer present:

Replace configuration parameter checkpoint_segments with min_wal_size and max_wal_size (Heikki Linnakangas)

If you previously adjusted checkpoint_segments, the following formula will give you an approximately equivalent setting:

max_wal_size = (3 * checkpoint_segments) * 16MB

Note that the default setting for max_wal_size is much higher than the default checkpoint_segments used to be, so adjusting it might no longer be necessary.

While pgtune is a really valuable tool it seems that it getting behind postgresql versions.

We are using "TB" as a unit in our PostgreSQL config (on box with 3TB memory):

oberstet@bvr-sql18:~/scm/3rdparty/pgtune$ sudo ./pgtune --type=dw /data/adr/postgresql.conf
Traceback (most recent call last):
  File "./pgtune", line 698, in <module>
    sys.exit(main(sys.argv))
  File "./pgtune", line 687, in main
    wizard_tune(config, options, settings)
  File "./pgtune", line 596, in wizard_tune
    config.update_setting(key, settings.show(key, value))
  File "./pgtune", line 275, in update_setting
    current = self.current_value(name)
  File "./pgtune", line 242, in current_value
    current = self.settings.parse(name, self.param_to_line[name].value())
  File "./pgtune", line 473, in parse
    return str(self.parse_int(name, value))
  File "./pgtune", line 456, in parse_int
    internal = int(value)
ValueError: invalid literal for int() with base 10: '2TB'

Any plans for 9.3 support?

It seems that we need support for 9.4 too.

pgtune is a great tool, don't let it die!

Subj.

The website link this GitHub repo points to, and the prior download link accessible through that site at http://pgfoundry.org/frs/download.php/2449/pgtune-0.9.3.tar.gz seem to be down. Unclear how long that has been the case.

Is that indicative of this project being unsupported now or a simple hosting/server error to resolve? Thanks!

Edit - Changed title for clarity.

[beans@intermine pgtune]$ psql --version
psql (PostgreSQL) 9.4.8

So that's what I'm running, but I tell pgtune that it's 9.1 since that's the latest settings file you've got in the repo:

[beans@intermine pgtune]$ ./pgtune -i postgresql.conf -o postgresql.conf.tuned -V 9.1 -c 100 -L
Traceback (most recent call last):
  File "./pgtune", line 698, in <module>
    sys.exit(main(sys.argv))
  File "./pgtune", line 687, in main
    wizard_tune(config, options, settings)
  File "./pgtune", line 593, in wizard_tune
    if settings.memory_unit(key):
  File "./pgtune", line 402, in memory_unit
    return (self.param_to_dict[setting])['memory_unit']
KeyError: 'wal_buffers'