Re: Unexpected "shared memory block is still in use"

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Unexpected "shared memory block is still in use"
Дата
Msg-id 6cefc482-b163-1c3d-48fd-344d99cb137f@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: Unexpected "shared memory block is still in use"  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 2019-09-04 16:59, Tom Lane wrote:
>> A related point, perhaps we should change the key printed into
>> postmaster.pid to be in hexadecimal format ("0x08x") so that it matches
>> what ipcs prints.
> Hmm, that depends on whose ipcs you use :-(.  A quick survey
> of my machines says it's
> 
>                 key     shmid
> 
> Linux:          hex     decimal
> FreeBSD:        decimal decimal
> NetBSD:         decimal decimal
> OpenBSD:        decimal decimal
> macOS:          hex     decimal
> HPUX:           hex     (not printed)
> 
> There's certainly room to argue that hex+decimal is most popular,
> but I'm not sure that that outweighs possible compatibility issues
> from changing postmaster.pid contents.  (Admittedly, it's not real
> clear that anything would be paying attention to the shmem key,
> so maybe there's no compatibility issue.)

Let's just leave it decimal then.  At least then it's easier to compare
it to ls -i output.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Plug-in common/logging.h with vacuumlo and oid2name
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Two pg_rewind patches (auto generate recovery conf and ensureclean shutdown)