Re: pg_hba_file_settings view patch

Поиск
Список
Период
Сортировка
От Haribabu Kommi
Тема Re: pg_hba_file_settings view patch
Дата
Msg-id CAJrrPGcoYB58yjWheAJJcvpBig4ifCDaYmJXDHADQ4QrzH2-mg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pg_hba_file_settings view patch  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Ответы Re: pg_hba_file_settings view patch
Список pgsql-hackers


On Tue, Nov 22, 2016 at 9:46 PM, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com> wrote:

It could be because of some un-initialised variable, which is
initialized appropriately by default on your machine but not on my
machine. I first applied your pg_hba_rules... patch, ran regression.
It didn't crash. then I applied patch for discard_hba... and it
started crashing. Does that give you any clue? Here's regression.out
file for make installcheck. Here is error log snippet that shows a
SIGSEGV there.
2016-11-22 15:47:11.939 IST [86206] LOG:  worker process: parallel
worker for PID 86779 (PID 86780) was terminated by signal 11:
Segmentation fault
2016-11-22 15:47:11.939 IST [86206] LOG:  terminating any other active
server processes
2016-11-22 15:47:11.939 IST [86779] WARNING:  terminating connection
because of crash of another server process
2016-11-22 15:47:11.939 IST [86779] DETAIL:  The postmaster has
commanded this server process to roll back the current transaction and
exit, because another server process exited abnormally and possibly
corrupted shared memory.

Applying those patches in any order doesn't matter.
 
I am not able to reproduce the crash both in debug and release mode
builds with both check and installcheck options.

Can you please share the back trace of the crash, so that it will be helpful
for me to locate the problem.
 
 
Regards,
Hari Babu
Fujitsu Australia

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

Предыдущее
От: Haribabu Kommi
Дата:
Сообщение: Re: macaddr 64 bit (EUI-64) datatype support
Следующее
От: Emre Hasegeli
Дата:
Сообщение: Re: Contains and is contained by operators of inet datatypes