| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel bitmap index scan |
| Date: | 2020-11-11 19:52:56 |
| Message-ID: | 451a127a-bbd2-1edc-f717-9852b5dc205f@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I took a look at this today, doing a bit of stress-testing, and I can
get it to crash because of segfaults in pagetable_create (not sure if
the issue is there, it might be just a symptom of an issue elsewhere).
Attached is a shell script I use to run the stress test - it's using
'test' database, generates tables of different size and then runs
queries with various parameter combinations. It takes a while to trigger
the crash, so it might depend on timing or something like that.
I've also attached two examples of backtraces. I've also seen infinite
loop in pagetable_create, but the crashes are much more common.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| backtraces.txt | text/plain | 10.1 KB |
| parallel-bitmap-index-scan.sh | application/x-shellscript | 5.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-11-11 19:57:49 | Re: Add docs stub for recovery.conf |
| Previous Message | Soumyadeep Chakraborty | 2020-11-11 19:49:57 | Re: Split copy.c |