On Thu, Jan 28, 2021 at 6:14 AM osumi.takami...@fujitsu.com
wrote:
>
> Hello
>
>
> On Thursday, January 21, 2021 11:19 PM I wrote:
> > If no one disagree with it, I'll proceed with (1) below.
> >
> > (1) writing the time or LSN in the control file to indicate when/where
> > wal_level
> > is chang
On Mon, 2021-03-15 at 17:32 -0400, Stephen Frost wrote:
> We explicitly document that people can switch the WAL level and restart
> to do bulk data loads faster, and there's certainly no shortage of
> discussion (including what prompted this thread..) about doing exactly
> that. Adding more docume
Greetings,
* tsunakawa.ta...@fujitsu.com (tsunakawa.ta...@fujitsu.com) wrote:
> From: David Steele
> > As a backup software author, I don't see this feature as very useful.
> >
> > The problem is that there are lots of ways for WAL to go missing so
> > monitoring the WAL archive for gaps is esse
On Friday, March 12, 2021 5:04 PM Peter Eisentraut
wrote:
> On 08.03.21 03:45, osumi.takami...@fujitsu.com wrote:
> > OK. The basic idea is to enable backup management tools to recognize
> > wal_level drop between*snapshots*.
> > When you have a snapshot of the cluster at one time and another one
On 08.03.21 03:45, osumi.takami...@fujitsu.com wrote:
OK. The basic idea is to enable backup management
tools to recognize wal_level drop between*snapshots*.
When you have a snapshot of the cluster at one time and another one
at different time, with this new parameter, you can see if
anything tha
From: David Steele
> As a backup software author, I don't see this feature as very useful.
>
> The problem is that there are lots of ways for WAL to go missing so
> monitoring the WAL archive for gaps is essential and this feature would
> not replace that requirement. The only extra information y
On Tuesday, March 9, 2021 11:13 PM David Steele
> On 3/7/21 9:45 PM, osumi.takami...@fujitsu.com wrote:
> > On Sun, Mar 7, 2021 3:48 AM Peter Eisentraut
> wrote:
> >> On 28.01.21 01:44, osumi.takami...@fujitsu.com wrote:
> (1) writing the time or LSN in the control file to indicate
> wh
On 3/7/21 9:45 PM, osumi.takami...@fujitsu.com wrote:
On Sun, Mar 7, 2021 3:48 AM Peter Eisentraut
wrote:
On 28.01.21 01:44, osumi.takami...@fujitsu.com wrote:
(1) writing the time or LSN in the control file to indicate
when/where wal_level is changed to 'minimal'
from upper level to invalida
On Sun, Mar 7, 2021 3:48 AM Peter Eisentraut
wrote:
> On 28.01.21 01:44, osumi.takami...@fujitsu.com wrote:
> >> (1) writing the time or LSN in the control file to indicate
> >> when/where wal_level is changed to 'minimal'
> >> from upper level to invalidate the old backups or make alerts to user
On 28.01.21 01:44, osumi.takami...@fujitsu.com wrote:
(1) writing the time or LSN in the control file to indicate when/where wal_level
is changed to 'minimal'
from upper level to invalidate the old backups or make alerts to users.
I attached the first patch which implementes this idea.
It was al
Hello
On Thursday, January 21, 2021 11:19 PM I wrote:
> If no one disagree with it, I'll proceed with (1) below.
>
> (1) writing the time or LSN in the control file to indicate when/where
> wal_level
> is changed to 'minimal'
> from upper level to invalidate the old backups or make alerts to us
Hi
Apologies for my delay.
On Wednesday, January 6, 2021 7:03 PM I wrote:
> I'll continue the discussion of [2].
> We talked about how to recognize the time or LSN when/where wal_level is
> changed to 'none' there.
>
> You said
> > The use case I imagined is that the user temporarily changes wal
Greetings,
* osumi.takami...@fujitsu.com (osumi.takami...@fujitsu.com) wrote:
> On Thursday, January 7, 2021 2:40 AM Stephen Frost wrote:
> > * osumi.takami...@fujitsu.com (osumi.takami...@fujitsu.com) wrote:
> > > You said
> > > > The use case I imagined is that the user temporarily changes
> >
Hi Stephen
Thank you so much for replying !
On Thursday, January 7, 2021 2:40 AM Stephen Frost wrote:
> * osumi.takami...@fujitsu.com (osumi.takami...@fujitsu.com) wrote:
> > You said
> > > The use case I imagined is that the user temporarily changes
> > > wal_level to 'none' from 'replica' or '
From: osumi.takami...@fujitsu.com
> I wondered, couldn't backup management tools utilize the information
> in the backup that is needed to be made when wal_level is changed to "none"
> for example ?
IIRC, someone proposed in the original thread that the change count can be
recorded in pg_control
Greetings,
* osumi.takami...@fujitsu.com (osumi.takami...@fujitsu.com) wrote:
> You said
> > The use case I imagined is that the user temporarily
> > changes wal_level to 'none' from 'replica' or 'logical' to speed up loading
> > and
> > changes back to the normal. In this case, the backups take
Hello, Sawada-san
I'll continue the discussion of [2].
We talked about how to recognize the time or LSN
when/where wal_level is changed to 'none' there.
You said
> The use case I imagined is that the user temporarily
> changes wal_level to 'none' from 'replica' or 'logical' to speed up loading
17 matches
Mail list logo
