On Thu, Oct 23, 2025 at 4:24 PM Scot Kreienkamp <
[email protected]> wrote:
>
> I always assumed streaming would “just work” as long as it’s the same
> major PG version and Linux-to-Linux regardless of OS/glibc versionIt
> never occurred to me that there could be an OS influencing f
On Thu, 2025-10-23 at 21:54 +, Dmitry Litvintsev wrote:
> I have been setting PITR backup off of base backup. Wal files are shipped to
> the host running pg_basebackup pulling backup from master host.
>
> Once base backup finished I wanted to try recovery.
>
> I added
>
> restore_command =
> On Oct 23, 2025, at 1:52 PM, Peter J. Holzer wrote:
>
> On 2025-10-20 06:43:17 -0600, Rob Sargent wrote:
>>
>>
On Oct 20, 2025, at 5:05 AM, Peter J. Holzer wrote:
>>>
>>> On 2025-10-19 20:32:07 -0600, Rob Sargent wrote:
>> On Oct 19, 2025, at 2:38 PM, Rich Shepard
>> wro
Hello,
I have been setting PITR backup off of base backup. Wal files are shipped to
the host running pg_basebackup pulling backup from
master host.
Once base backup finished I wanted to try recovery.
I added
restore_command = 'gunzip /data/xlogs/%f.gz > %p'
(that command is wrapped in a s
Just wanted to clarify, this failed because OP used streaming which may not
work between OS versions? But logical would have been just fine, between OS
and PG versions or even to Windows? I always assumed streaming would “just
work” as long as it’s the same major PG version and Linux-to-Linux
On 2025-10-20 06:43:17 -0600, Rob Sargent wrote:
>
>
> > On Oct 20, 2025, at 5:05 AM, Peter J. Holzer wrote:
> >
> > On 2025-10-19 20:32:07 -0600, Rob Sargent wrote:
> On Oct 19, 2025, at 2:38 PM, Rich Shepard
> wrote:
> >>> On Sun, 19 Oct 2025, Rob Sargent wrote:
> I think yo
On Fri, 24 Oct 2025 at 07:17, Devrim Gündüz wrote:
> This happens because of the glibc version differrence between RHEL X and RHEL
> Y. At this point you either have to rebuild all indexes (sorry!) or redo the
> upgrade via logical replication (if it works for your app's behaviour)
There was a
Hi,
This happens because of the glibc version differrence between RHEL X and RHEL
Y. At this point you either have to rebuild all indexes (sorry!) or redo the
upgrade via logical replication (if it works for your app's behaviour)
Devrim
On 22 October 2025 12:03:06 EEST, Bala M wrote:
>Hi Tea
On Thu, Oct 23, 2025 at 11:21 AM Greg Sabino Mullane
wrote:
>
>>-
>>
>>*Acceptable downtime:* ~1 day
>>-
>>
>>*Logical replication:* Not feasible due to the number of schemas,
>>tables, and overall data volume
>>
>> I'm not sure why this is not feasible. Can you expand on this
On 10/23/25 07:51, Bala M wrote:
Hi All,
Thank you for the valuable responses regarding the *index corruption
issue* we observed during our test migration of a *PostgreSQL 11*
environment from *RHEL 7 to RHEL 9* using *streaming replication*.
Based on the replies, I understand that.
S
>
>
>-
>
>*Acceptable downtime:* ~1 day
>-
>
>*Logical replication:* Not feasible due to the number of schemas,
>tables, and overall data volume
>
> I'm not sure why this is not feasible. Can you expand on this?
* For a *15 TB database* with roughly *1 day downtime*, what would
11 matches
Mail list logo
