回复：Re: PANIC: wrong buffer passed to visibilitymap_clear
| От | 王伟(学弈) |
|---|---|
| Тема | 回复：Re: PANIC: wrong buffer passed to visibilitymap_clear |
| Дата | |
| Msg-id | 0bd04b33-5f37-478b-9426-55544f667318.rogers.ww@alibaba-inc.com обсуждение исходный текст |
| Ответ на | Re: PANIC: wrong buffer passed to visibilitymap_clear (Tomas Vondra <tomas.vondra@enterprisedb.com>) |
| Ответы |
Re: 回复：Re: PANIC: wrong buffer passed to visibilitymap_clear
(Tomas Vondra <tomas.vondra@enterprisedb.com>)
|
| Список | pgsql-hackers |
On 7/22/22 18:06, Tomas Vondra wrote:
> Which PG14 version / commit is this, exactly? What sysbench parameters
> did you use, how likely is hitting the issue?
> did you use, how likely is hitting the issue?
PG_VERSION is '14beta2'.
The head commit id is 'e1c1c30f635390b6a3ae4993e8cac213a33e6e3f'.
I have run these sysbench commands for couple of days, but only two times to hit the issue.
These sysbench commands are:
prepare:
sysbench --tables=10 --table-size=1000000 --db-ps-mode=auto --pgsql-password=* --time=72000 --db-driver=pgsql --pgsql-port=* --threads=50 --thread-init-timeout=3000 --report-interval=5 --pgsql-user=* --pgsql-host=* --pgsql-db=* --events=0 --pgsql-ignore-errors="PX000,58M01" ./src/lua/oltp_insert.lua prepare
parallel execution:
sysbench --tables=10 --table-size=1000000 --db-ps-mode=auto --pgsql-password=* --time=72000 --db-driver=pgsql --pgsql-port=* --threads=50 --thread-init-timeout=3000 --report-interval=5 --pgsql-user=* --pgsql-host=* --pgsql-db=* --events=0 --pgsql-ignore-errors="PX000,58M01" ./src/lua/oltp_insert.lua run
sysbench --tables=10 --table-size=1000000 --db-ps-mode=auto --pgsql-password=* --time=72000 --db-driver=pgsql --pgsql-port=* --threads=50 --thread-init-timeout=3000 --report-interval=5 --pgsql-user=* --pgsql-host=*--pgsql-db=* --events=0 --pgsql-ignore-errors="PX000,58M01" ./src/lua/oltp_delete.lua run
sysbench --tables=10 --table-size=1000000 --db-ps-mode=auto --pgsql-password=* --time=72000 --db-driver=pgsql --pgsql-port=* --threads=50 --thread-init-timeout=3000 --report-interval=5 --pgsql-user=* --pgsql-host=* --pgsql-db=* --events=0 --pgsql-ignore-errors="PX000,58M01" ./src/lua/oltp_read_write.lua run
sysbench --tables=10 --table-size=1000000 --db-ps-mode=auto --pgsql-password=* --time=72000 --db-driver=pgsql --pgsql-port=* --threads=50 --thread-init-timeout=3000 --report-interval=5 --pgsql-user=* --pgsql-host=* --pgsql-db=* --events=0 --pgsql-ignore-errors="PX000,58M01" ./src/lua/oltp_update_index.lua run
--
regards,
rogers.ww
------------------------------------------------------------------
发件人：Tomas Vondra<tomas.vondra@enterprisedb.com>
日 期：2022年07月22日 18:06:21
收件人：王伟(学弈)<rogers.ww@alibaba-inc.com>; pgsql-hackers<pgsql-hackers@lists.postgresql.org>
主 题：Re: PANIC: wrong buffer passed to visibilitymap_clear
On 7/22/22 10:22, 王伟(学弈) wrote:
> Hi,
> I recently find this problem while testing PG14 with sysbench.
> Then I look through the emails from pgsql-hackers and find a previous
> similary bug which
> is https://www.postgresql.org/message-id/flat/2247102.1618008027%40sss.pgh.pa.us
> <https://www.postgresql.org/message-id/flat/2247102.1618008027%40sss.pgh.pa.us>.
> But the bugfix commit(34f581c39e97e2ea237255cf75cccebccc02d477) is
> already patched to PG14.
>
Which PG14 version / commit is this, exactly? What sysbench parameters
did you use, how likely is hitting the issue?
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления:
Следующее
От: Pavel StehuleДата:
Сообщение: proposal - enhancing plpgsql's FOREACH statement for support json type