Re: BUG #15063: Updates to temporary tables fail when there is a publication with FOR ALL TABLES

Thanks David, I'm a Gentoo user... so actually I do... I can test (for
my use case at least) any candidate fixes etc.... just need to know
what/where they are.

I'm a C/C++ developer by profession... so I don't mind get my hands a
little dirty there if I can be of some help.

Regards

Dan

On 13/02/18 21:11, David G. Johnston wrote:
> On Tuesday, February 13, 2018, PG Bug reporting form
> <noreply(at)postgresql(dot)org <mailto:noreply(at)postgresql(dot)org>> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference:      15063
> Logged by:          Dan Goodliffe
> Email address: dan(at)randomdan(dot)homeip(dot)net
> <mailto:dan(at)randomdan(dot)homeip(dot)net>
> PostgreSQL version: 10.2
> Operating system:   Linux
> Description:
>
> Given a publication which uses FOR ALL TABLES, so that future
> tables are
> included...
>
> [...]
>
> I'm not sure if the temporary table has been added to the
> publication (which
> isn't supported) or if the presence of the FOR ALL TABLES
> publication alone
> (without the table being added to it) is enough to trigger the
> problem.
>
> I can provide more debug/details etc if required given an idea of
> what's
> needed and how to get it.
>
>
> A similar report regarding materialized views came through the other
> week and though I haven't seen a patch as of yet I believe the cause
> is at least understood.  Unfortunately a minor release just came out
> so it will be a couple of months proabaly before a fix is released -
> unless you can compile from source (for production if not just for
> testing purposes).
>
> For now, "for all tables" mode is broken unless all you really have
> are normal tables.
>
> David J.
>

--
Dan Goodliffe
dan(at)randomdan(dot)homeip(dot)net
07970 523693