Jim Nasby wrote:
Yeah, especially since you mentioned this being for backups. I
suspect you *want* those WAL records marked with 0, because that
tells you that you can't rely on WAL when you back that data up.
Thanks, you right if you doing incremental backup you try compare every
page LSN wi
On 8/26/16 4:17 PM, Andres Freund wrote:
On 2016-08-26 18:46:42 +0300, Yury Zhuravlev wrote:
Thanks all.
Now understand LSN strongly connected with WAL.
However how difficult put last system LSN instead 0?
It's not so important but will allow make use LSN more consistent.
Maybe explain why you
On 2016-08-26 18:46:42 +0300, Yury Zhuravlev wrote:
> Thanks all.
> Now understand LSN strongly connected with WAL.
> However how difficult put last system LSN instead 0?
> It's not so important but will allow make use LSN more consistent.
Maybe explain why you're interested in page lsns, that'd p
On Fri, Aug 26, 2016 at 10:46 AM, Yury Zhuravlev
wrote:
> Now understand LSN strongly connected with WAL.
> However how difficult put last system LSN instead 0?
> It's not so important but will allow make use LSN more consistent.
There might be performance implications when flushing the index
bu
Amit Kapila wrote:
On Thu, Aug 25, 2016 at 7:55 PM, Yury Zhuravlev
wrote:
Hello hackers.
I have a small question. While working on an incremental
backup I noticed a
strange thing.
Newly created index is contains the invalid LSN (0/0).
Exmaple: ...
For some of the indexes like btree which a
On Thu, Aug 25, 2016 at 7:55 PM, Yury Zhuravlev
wrote:
> Hello hackers.
>
> I have a small question. While working on an incremental backup I noticed a
> strange thing.
> Newly created index is contains the invalid LSN (0/0).
> Exmaple:
> postgres=# select lsn from page_header(get_raw_page('test_a
On Thu, Aug 25, 2016 at 1:13 PM, Robert Haas wrote:
> On Thu, Aug 25, 2016 at 10:25 AM, Yury Zhuravlev
> wrote:
>> I have a small question. While working on an incremental backup I noticed a
>> strange thing.
>> Newly created index is contains the invalid LSN (0/0).
>> Exmaple:
>> postgres=# sele
On Thu, Aug 25, 2016 at 10:25 AM, Yury Zhuravlev
wrote:
> I have a small question. While working on an incremental backup I noticed a
> strange thing.
> Newly created index is contains the invalid LSN (0/0).
> Exmaple:
> postgres=# select lsn from page_header(get_raw_page('test_a_idx2',0));
> lsn
Hello hackers.
I have a small question. While working on an incremental backup I noticed a
strange thing.
Newly created index is contains the invalid LSN (0/0).
Exmaple:
postgres=# select lsn from page_header(get_raw_page('test_a_idx2',0));
lsn
-
0/0
(1 row)
Can you explain me why?
Than