From: | Brad White <b55white(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Setting up replication on Windows, v9.4 |
Date: | 2022-11-11 03:24:02 |
Message-ID: | 0d0361ba-223d-7e4b-1f44-337cfedab3b9@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/7/2022 3:42 PM, Rob Sargent wrote:
> > Care to share some of the ways the app stopped working? You might
> get a leg up on where best to remediate.
I don't recall, as that was a few months ago.
We are running MS-Access as a front end with Postgres as the back end.
It appeared to read and write data perfectly fine, but failed in the
business logic on the Access side where there didn't appear to be any DB
involvement. But switching to v14 caused it and switching away fixed it.
No obvious cause that I could see.
As written, switching databases was very time-consuming.
Since then, I've rewritten the app so that the network admin just
changes an INI file that the app reads on start up.
If there is a change, it switches all the tables over in about 15 seconds.
We wanted that ability anyway in case we ever needed to switch to using
the backup server.
Now, I am working on getting replication going.
Next up: back to upgrading.
But, since you ask, I'll post here when I get back to that so y'all can
follow along as I narrow it down to a specific version.
From | Date | Subject | |
---|---|---|---|
Next Message | Brad White | 2022-11-11 03:25:53 | Re: Setting up replication on Windows, v9.4 |
Previous Message | 黄宁 | 2022-11-11 02:47:43 | get table oid in GIN extracequery function |