Re: pgsql: ltree: Zero padding bytes when allocating memory for externally
От | Tom Lane |
---|---|
Тема | Re: pgsql: ltree: Zero padding bytes when allocating memory for externally |
Дата | |
Msg-id | 3431.1457625479@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pgsql: ltree: Zero padding bytes when allocating memory for externally (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pgsql: ltree: Zero padding bytes when allocating
memory for externally
|
Список | pgsql-committers |
I wrote: > Andres Freund <andres@anarazel.de> writes: >> This is marked as the originating commit for a failure on dromedary: >> http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=dromedary&dt=2016-03-08%2023%3A27%3A02 >> the origin of the failure is: >> FATAL: no PostgreSQL user name specified in startup packet >> while in the 'comments' tests, which looks fairly independent of this commit. >> Tom, did you happen to change config on that machine or anything? > No, haven't touched it in awhile. Looks like just a glitch maybe? I had a vague feeling that this looked familiar, and it occurred to me to scan the buildfarm database for occurrences of that error message. Quite a few hours later, I have these results: sysname | snapshot | count -----------+---------------------+------- okapi | 2012-05-10 06:15:02 | 138 okapi | 2012-05-20 00:15:02 | 174 dromedary | 2014-03-28 00:13:52 | 4 dromedary | 2014-05-07 06:23:09 | 2 dromedary | 2016-03-08 23:27:02 | 2 So yeah, we've seen it before, but it sure looks like a system-specific glitch. dromedary is a pretty old machine (2006 Mac mini), so I would not be surprised if it dropped a bit now and then. regards, tom lane
В списке pgsql-committers по дате отправления: