Re: increase message string buffer size of watch command of psql
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ioseph Kim <pgsql-kr@postgresql.kr>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2016-06-15T02:56:56Z
Lists: pgsql-hackers
Ioseph Kim <pgsql-kr@postgresql.kr> writes: > 2016 06 15 01:56 Tom Lane () : >> I take it from the vast silence that nobody particularly cares one way >> or the other. On reflection I think that this would be a good change >> to make, so I'll go do so unless I hear complaints soon. regards, tom >> lane > I propose to change from asctime() to sql current_timestamp value, > then users will change date format with set command DateStyle. That would require an additional SQL query each time through the loop, which seems like undue expense. It's also not terribly friendly to the goal of localization, I should think, given the limited number of datestyle options and the fact that none of them actually change day or month names to non-English choices. And it would imply changing the timestamps from psql's timezone to the backend's. While that might have been a good way to do it in a green field, it's not the way \watch has worked in the past, and given the lack of complaints I'm disinclined to change that. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Improve header output from psql's \watch command.
- dea2b5960a94 9.6.0 cited