Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support TB unit in config literals #15

Open
oberstet opened this issue Nov 21, 2015 · 0 comments
Open

Support TB unit in config literals #15

oberstet opened this issue Nov 21, 2015 · 0 comments

Comments

@oberstet
Copy link

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'
oberstet pushed a commit to oberstet/pgtune that referenced this issue Nov 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant