On Thu, Apr 8, 2021 at 3:53 PM Bharath Rupireddy
wrote:
>
> On Thu, Apr 8, 2021 at 3:34 PM Magnus Hagander wrote:
> >
> > Looking at
> > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2021-04-08%2009%3A43%3A13
> > which broke with the patch to add pg_wait_backend_termination().
On Thu, Apr 8, 2021 at 3:34 PM Magnus Hagander wrote:
>
> Looking at
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2021-04-08%2009%3A43%3A13
> which broke with the patch to add pg_wait_backend_termination().
>
> AFAICT the change is that the order of rows coming back from "SE
On Thu, Apr 8, 2021 at 12:22 PM Peter Eisentraut
wrote:
>
> On 08.04.21 12:04, Magnus Hagander wrote:
> > Looking at
> > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2021-04-08%2009%3A43%3A13
> > which broke with the patch to add pg_wait_backend_termination().
> >
> > AFAICT t
On 08.04.21 12:04, Magnus Hagander wrote:
Looking at
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2021-04-08%2009%3A43%3A13
which broke with the patch to add pg_wait_backend_termination().
AFAICT the change is that the order of rows coming back from "SELECT
routine_name, seq
Looking at
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2021-04-08%2009%3A43%3A13
which broke with the patch to add pg_wait_backend_termination().
AFAICT the change is that the order of rows coming back from "SELECT
routine_name, sequence_name FROM
information_schema.routine_s