| From: | Álvaro Hernández Tortosa <aht(at)nosys(dot)es> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org, Greg Smith <gsmith(at)gregsmith(dot)com> |
| Subject: | Re: RFC: programmable file format for postgresql.conf |
| Date: | 2013-12-07 03:28:22 |
| Message-ID: | 52A295D6.8080105@nosys.es |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/12/2013 22:59, Peter Eisentraut wrote:
> On 12/6/13, 12:29 PM, Álvaro Hernández Tortosa wrote:
>> What I've been trying to do is summarize what has already been
>> discussed here and propose a solution. You say that "you can already do
>> those thisngs", but that's not what I have read here. Greg Smith (cc'ed
>> as I'm quoting you) was explaining this in [1]:
>>
>> "Right now, writing such a tool in a generic way gets so bogged down
>> just in parsing/manipulating the postgresql.conf file that it's hard to
>> focus on actually doing the tuning part."
> That was in 2008. I don't think that stance is accurate anymore.
Just for me to learn about this: why is it not accurate anymore?
Thanks for your patience! :)
aht
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Hernández Tortosa | 2013-12-07 03:28:51 | Re: RFC: programmable file format for postgresql.conf |
| Previous Message | Michael Paquier | 2013-12-07 03:00:45 | Re: Recovery to backup point |