Note that WAL replication replicates *the whole instance* not just specific
databases. You need logical replication for that.
Also, I just learned that 9.4 *does* have WAL replication slots (which makes
replication *much* easier). v9.6 is where replication is "like rolling off
a log"
Cranking up the log_min_messages level might help, to see what is (or is
not) reaching the server.
On 11/11/22 14:35, Brad White wrote:
> Or manually running the application queries?
That was the odd thing. It didn't appear to be in the middle of running
any queries. The database shouldn't
> Or manually running the application queries?
That was the odd thing. It didn't appear to be in the middle of running any
queries. The database shouldn't have had any effect.
> Anyway, try Pg 9.6.
I have Pg 12 installed, so I'll try that.
I'll start a new thread on my adventures in upgrading.
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
From the error log:
FATAL: hot standby is not possible because wal_level was not
set to "hot_standby" or higher on the master server
HINT: Either set wal_level to "hot_standby" on the master, or
turn off hot_standby here.
I tried setting hot_standby to off, but that
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
On 11/7/22 13:59, Brad White wrote:
> v9.4 has been EOL for 2 years 9 months.
As I said, the next step will be to upgrade.
It would make sense to upgrade first, since "there have been some big
advances since then which make replication much easier"
But when we upgraded, the app stopped
>
>
> > v9.4 has been EOL for 2 years 9 months.
As I said, the next step will be to upgrade.
It would make sense to upgrade first, since "there have been some big
advances since then which make replication much easier"
But when we upgraded, the app stopped working.
So I'll need to go through and
On 11/4/22 17:59, Brad White wrote:
I'm setting up a backup for our primary postgres server using the archived
WAL files.
Then I'll try to upgrade it to Streaming Replication.
Then I'll upgrade the system to v.latest.
For now, we are on v.9.4.
FYI: v9.4 has been EOL for 2 years 9 months.
2022年11月5日(土) 10:02 Ian Lawrence Barwick :
>
> 2022年11月5日(土) 7:59 Brad White :
...
> > Interestingly, the recovery file says
> > # Note that recovery.conf must be in $PGDATA directory.
> > # It should NOT be located in the same directory as postgresql.conf
> > Those seem contradictory.
>
> I don't
2022年11月5日(土) 7:59 Brad White :
>
> I'm setting up a backup for our primary postgres server using the archived
> WAL files.
> Then I'll try to upgrade it to Streaming Replication.
> Then I'll upgrade the system to v.latest.
> For now, we are on v.9.4.
>
> I do a base backup from the primary to a
I'm setting up a backup for our primary postgres server using the archived
WAL files.
Then I'll try to upgrade it to Streaming Replication.
Then I'll upgrade the system to v.latest.
For now, we are on v.9.4.
I do a base backup from the primary to a directory on the NAS.
"C:\Program
12 matches
Mail list logo
