| From: | "Anton A(dot) Melnikov" <aamelnikov(at)inbox(dot)ru> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | [BUG] Crash on pgbench initialization. |
| Date: | 2023-07-23 20:21:47 |
| Message-ID: | ae46f2fb-5586-3de0-b54b-1bb0f6410ebd@inbox.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello!
My colleague Victoria Shepard reported that pgbench might crash
during initialization with some values of shared_buffers and
max_worker_processes in conf.
After some research, found this happens when the LimitAdditionalPins() returns exactly zero.
In the current master, this will happen e.g. if shared_buffers = 10MB and max_worker_processes = 40.
Then the command "pgbench --initialize postgres" will lead to crash.
See the backtrace attached.
There is a fix in the patch applied. Please take a look on it.
With the best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| Attachment | Content-Type | Size |
|---|---|---|
| bt.txt | text/plain | 16.6 KB |
| v1-0001-nonzero-from-LimitAdditionalPins.patch | text/x-patch | 744 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2023-07-23 21:29:46 | Re: Row pattern recognition |
| Previous Message | Tom Lane | 2023-07-23 20:03:36 | Re: multiple membership grants and information_schema.applicable_roles |