Fix volatile vs. pointer confusion - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Fix volatile vs. pointer confusion
Date
Msg-id f747368d-9e1a-c46a-ac76-3c27da32e8e4@2ndquadrant.com
Whole thread Raw
Responses Re: Fix volatile vs. pointer confusion
Re: Fix volatile vs. pointer confusion
Re: Fix volatile vs. pointer confusion
List pgsql-hackers
Variables used after a longjmp() need to be declared volatile.  In
case of a pointer, it's the pointer itself that needs to be declared
volatile, not the pointed-to value.  So we need

    PyObject *volatile items;

instead of

    volatile PyObject *items;  /* wrong */

Attached patch fixes a couple of cases of that.  Most instances were
already correct.

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

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: A separate table level option to control compression
Next
From: Andy Fan
Date:
Subject: I have some troubles to run test_shm_mq;