| From: | Ron <ronljohnsonjr(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 18:38:22 |
| Message-ID: | d16276ef-8060-b208-3309-87205541b02c@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/10/22 21:24, Brad White wrote:
> 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.
Nothing in the application error logs? What about the Postgresql error
logs? Or manually running the application queries?
Anyway, try Pg 9.6. Still EOL, but /not as/ EOL.
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2022-11-11 18:46:24 | Re: Table : Bloat grow high |
| Previous Message | Tom Lane | 2022-11-11 17:27:46 | Re: pg_isready mandatory parameters? |