On Wed, 6 Jan 2021 at 18:23, Peter Eisentraut <
peter.eisentr...@2ndquadrant.com> wrote:
> On 2021-01-06 00:30, Craig Ringer wrote:
> > Perhaps debug_invalidate_system_caches_always ? It's a bit long but we
> > use the debug prefix elsewhere too.
>
> Committed with that name.
>
Thanks very much.
On 2021-01-06 00:30, Craig Ringer wrote:
Perhaps debug_invalidate_system_caches_always ? It's a bit long but we
use the debug prefix elsewhere too.
Committed with that name.
In your original patch, this hunk in pg_config_manual.h:
+ * You can define these by editing pg_config_manual.h but it'
On Tue, 5 Jan 2021, 22:41 Peter Eisentraut, <
peter.eisentr...@2ndquadrant.com> wrote:
> On 2020-12-03 07:01, Craig Ringer wrote:
> > To try it out, apply the patch (git am), build with --enable-cassert,
> > then compare:
> >
> > make -C src/test/regress check
> >
> > and
> >
> > PGOPTIONS
On 2020-12-03 07:01, Craig Ringer wrote:
To try it out, apply the patch (git am), build with --enable-cassert,
then compare:
make -C src/test/regress check
and
PGOPTIONS="-c debug_clobber_cache_depth=1" \
make -C src/test/regress check
The speed difference will be obvious if noth
On Thu, 3 Dec 2020 at 15:53, Craig Ringer wrote:
>
> On Tue, 27 Oct 2020 at 16:34, Peter Eisentraut <
> peter.eisentr...@2ndquadrant.com> wrote:
>
>> On 2020-09-25 09:40, Craig Ringer wrote:
>> > While working on extensions I've often wanted to enable cache
>> clobbering
>> > for a targeted piece
On Tue, 27 Oct 2020 at 16:34, Peter Eisentraut <
peter.eisentr...@2ndquadrant.com> wrote:
> On 2020-09-25 09:40, Craig Ringer wrote:
> > While working on extensions I've often wanted to enable cache clobbering
> > for a targeted piece of code, without paying the price of running it for
> > all bac
On Mon, 30 Nov 2020, 20:38 Anastasia Lubennikova, <
a.lubennik...@postgrespro.ru> wrote:
> On 27.10.2020 11:34, Peter Eisentraut wrote:
> > On 2020-09-25 09:40, Craig Ringer wrote:
> >> While working on extensions I've often wanted to enable cache
> >> clobbering for a targeted piece of code, with
On 27.10.2020 11:34, Peter Eisentraut wrote:
On 2020-09-25 09:40, Craig Ringer wrote:
While working on extensions I've often wanted to enable cache
clobbering for a targeted piece of code, without paying the price of
running it for all backends during postgres startup and any initial
setup tas
On 2020-09-25 09:40, Craig Ringer wrote:
While working on extensions I've often wanted to enable cache clobbering
for a targeted piece of code, without paying the price of running it for
all backends during postgres startup and any initial setup tasks that
are required.
So here's a patch that
