Is pg_log_standby_snapshot() expected to cause a WAL segment to be emitted
in an otherwise idle system? In my lab setup, the primary did not, despite
invoking pg_log_standby_snapshot() on it, even when several times the
archive_timeout value passed after using that function.
The setup was all
own and static schema is better than showing it? In my case (tracking
down
execution differences between local and FDW view use) this has occupied a
lot of
time.
Thanks again,
Pete O'Such
, but Postgres
always executes a qualified version of the view query, seemingly determined
upon creation of the view.
That implies the final qualifier is stored by Postgres, but I don't know
how to show it.
Thanks,
Pete O'Such
:46 AM Tom Lane wrote:
> "Pete O'Such" writes:
> > I've got a view on server A (PG 15.2) that fails when queried via FDW
> from
> > server B (also PG 15.2). Querying it as a foreign table from server B
> > yields a message like "ERROR: function blah(type
I've got a view on server A (PG 15.2) that fails when queried via FDW from
server B (also PG 15.2). Querying it as a foreign table from server B
yields a message like "ERROR: function blah(type) does not exist".
Confusingly, I succeed when: I log into server A, set my role to match the
role
Yup, FIPS-mode is on for both ends. I'd love a pointer to docs or other
resources for figuring out what the path forward looks like.
Thanks for the fast and insightful diagnostic tip..
-Pete O'Such
On Mon, Apr 18, 2022 at 5:08 PM Tom Lane wrote:
> Adrian Klaver writes:
> > On 4/18
ver A's PG 11. I hit this same error and
shifted to troubleshooting with just psql but kept getting the error.
I've checked for md5 use on both servers, but I still don't see a role for
that with psql on Server B's psql.
What can I do to get authentication working?
Thanks,
Pete O'Such
