pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brad White <b55white@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Setting up replication on Windows, v9.4
Date: Thu, 10 Nov 2022 21:24:02 -0600
Message-ID: <0d0361ba-223d-7e4b-1f44-337cfedab3b9@gmail.com> (raw)
In-Reply-To: <b11fec98-bc56-171a-5b72-d8387f25edb7@gmail.com>
References: <CAA_1=93vc6szcOe-F4W7FwAZkXCrC2-ODY6GV7C8CtQfbg0V0Q@mail.gmail.com>
	<c86a03f3-402e-5ca2-2632-ba7a26d1dd94@gmail.com>
	<CAA_1=90CtGfMvhUFsz0nfDCzA+9BLGPtbpG9WBd+rjWH67Fotg@mail.gmail.com>
	<b11fec98-bc56-171a-5b72-d8387f25edb7@gmail.com>


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.

view thread (12+ messages)  latest in thread

Message-ID: <0d0361ba-223d-7e4b-1f44-337cfedab3b9@gmail.com>
Permalink:  ../0d0361ba-223d-7e4b-1f44-337cfedab3b9@gmail.com/
Also on:    postgresql.org/message-id/0d0361ba-223d-7e4b-1f44-337cfedab3b9@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: b55white@gmail.com
  Subject: Re: Setting up replication on Windows, v9.4
  In-Reply-To: <0d0361ba-223d-7e4b-1f44-337cfedab3b9@gmail.com>
  References: <CAA_1=93vc6szcOe-F4W7FwAZkXCrC2-ODY6GV7C8CtQfbg0V0Q@mail.gmail.com> <c86a03f3-402e-5ca2-2632-ba7a26d1dd94@gmail.com> <CAA_1=90CtGfMvhUFsz0nfDCzA+9BLGPtbpG9WBd+rjWH67Fotg@mail.gmail.com> <b11fec98-bc56-171a-5b72-d8387f25edb7@gmail.com> <0d0361ba-223d-7e4b-1f44-337cfedab3b9@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox