tion '* raise ERROR test *';
>
> END $$;
>
> When I execute that through PSQL this is returned:
>
> shgroup02s=> call part.test2();
> ERROR: * raise ERROR test *
>
> And in the log file I see this written:
>
> 2022-09-07 12:58:00
> UTC:10.210.119.217(42434):postgres@shgroup02s:[15409]:ERROR: * raise
> ERROR test *
> 2022-09-07 12:58:00
> UTC:10.210.119.217(42434):postgres@shgroup02s:[15409]:CONTEXT: PL/pgSQL
> function part.test2() line 6 at RAISE
> 2022-09-07 12:58:00
> UTC:10.210.119.217(42434):postgres@shgroup02s:[15409]:STATEMENT: call
> part.test2();
>
> So the raise exception gets written to the log file when I execute it through
> PSQL which I believe is expected.
>
> I believe this clearly points to an issue with pg_cron. Would you agree?
>
> Regards
> Steve
>
>
--
Regards
Junwang Zhao
ory Solutions Suzhou Co.,Ltd (PFSS) R&D Center
>
> TEL：+86-(0)512-80991188-393 FAX：+86-(0)512-62957913
>
> **********
>
>
--
Regards
Junwang Zhao
s timetz need more bytes (8 vs 12) than timestamptz?
--
Regards
Junwang Zhao
lect pg_column_size(js) from x; -- return 33.
>
> based on src/include/utils/jsonb.h
> The key and value part is 20 bytes (is it correct?), Jsonb->vl_len_ is 4
> byte, JsonbContainer->header is 4 bytes. That's 28 bytes.
>
> but now on-disk is 33 bytes.
> so I am not sure where the remaining bytes are.
>
>
>
>
>
--
Regards
Junwang Zhao
its.
> > If that's not the case you'll need more calls to random())
> >
> > hp
> >
> > --
> >_ | Peter J. Holzer| Story must make more sense than reality.
> > |_|_) ||
> > | | | h...@hjp.at |-- Charles Stross, "Creative writing
> > __/ | http://www.hjp.at/ | challenge!"
>
>
--
Regards
Junwang Zhao
>
> > >
> > >
> > > Kind regards,
> > > Sean
> > >
> >
> >
> > --
> > Adrian Klaver
> > adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>
> >
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>
>
>
--
Regards
Junwang Zhao
