On Fri, May 24, 2013 at 3:24 PM, Amit Langote wrote:
> On Sat, May 25, 2013 at 3:08 AM, German Becker
> wrote:
> > Thanks Amit, I understand now. Is there a way to know/predict how many
> > prealocated segments will there be in a certain moment? What does it
> deppend
> > on?
>
> Upthread, Fujii
On Sat, May 25, 2013 at 3:08 AM, German Becker wrote:
> Thanks Amit, I understand now. Is there a way to know/predict how many
> prealocated segments will there be in a certain moment? What does it deppend
> on?
Upthread, Fujii Masao-san suggested what might have happened that
caused these pre-al
Thanks Amit, I understand now. Is there a way to know/predict how many
prealocated segments will there be in a certain moment? What does it
deppend on?
On Fri, May 24, 2013 at 12:46 PM, Amit Langote wrote:
> > I didn't quite understand what you mean by that... But anyways so do you
> > people th
> I didn't quite understand what you mean by that... But anyways so do you
> people think this sequence number overlap is "normal" ?
There is "no overlap" at all. The newer segments that you see are
"pre-allocated" ones. They have not been written to yet.
>From the "ls -l pg_xlog" output that you
On Fri, May 24, 2013 at 10:01 AM, Amit Langote wrote:
> > Maybe I didn't explain correctly. I am using COPY/pg_dump/pg_restore for
> > migration (and it is working fine). The streaming replication is for
> > hot-standby replication *once migrated*. Thing is I disbable archving and
> > set wal_leve
> Maybe I didn't explain correctly. I am using COPY/pg_dump/pg_restore for
> migration (and it is working fine). The streaming replication is for
> hot-standby replication *once migrated*. Thing is I disbable archving and
> set wal_level to minimal, when migrating the large portion of data, to make
Hi Sergey,
Maybe I didn't explain correctly. I am using COPY/pg_dump/pg_restore for
migration (and it is working fine). The streaming replication is for
hot-standby replication *once migrated*. Thing is I disbable archving and
set wal_level to minimal, when migrating the large portion of data, to
On Thu, May 23, 2013 at 6:18 AM, German Becker wrote:
> Let me describe the process I follow to get to this. What I am doing is
> testing a migration from 8.3 to 9.1. They way I plan to do it is the
> following.
> 1) Create the schema
> 2) import the biggest tables, which are not updated,only grow
On Thu, May 23, 2013 at 5:29 AM, Sergey Konoplev wrote:
> On Thu, May 23, 2013 at 1:25 AM, Amit Langote
> wrote:
> > Okay, now I understand. Also, looking at his "ls -l pg_xlog", I could
> > find that modified timestamps of all those pre-allocated segments are
> > about similar (around 12:10), w
On Thu, May 23, 2013 at 1:25 AM, Amit Langote wrote:
> Okay, now I understand. Also, looking at his "ls -l pg_xlog", I could
> find that modified timestamps of all those pre-allocated segments are
> about similar (around 12:10), whereas the latest modified time (15:37)
> is of segment 0001
>> Can pre-allocation go that further? for example, assuming
>> 0001000E0080 is currently being used, then is it possible
>> that a segment named/numbered 00010010007E (which does
>> exist in his pg_xlog as he reported in pgsql-admin thread) is
>> pre-allocated already?
>
>
On Thu, May 23, 2013 at 5:01 PM, Amit Langote wrote:
>> I think these are the WAL files that were preallocated by WAL
>> recycling but have not
>> been used yet.
>>
>>> # WAL after wal_level changed from 'minimal' to 'hot_standby'
>>>
>>> -rw--- 1 postgres postgres 16777216 May 21 12:27
>>> 0
> I think these are the WAL files that were preallocated by WAL
> recycling but have not
> been used yet.
>
>> # WAL after wal_level changed from 'minimal' to 'hot_standby'
>>
>> -rw--- 1 postgres postgres 16777216 May 21 12:27 0001000E007B
>> -rw--- 1 postgres postgres 16777216
On Thu, May 23, 2013 at 10:10 AM, Amit Langote wrote:
> A PostgreSQL user recently reported on pgsql-admin about an issue:
> when he changed wal_level from 'minimal' to 'hot_standby', the WAL
> segment sequence rewound, that is, it started using old names. A
> snippet of his "ls -lrt pg_xlog":
>
>
A PostgreSQL user recently reported on pgsql-admin about an issue:
when he changed wal_level from 'minimal' to 'hot_standby', the WAL
segment sequence rewound, that is, it started using old names. A
snippet of his "ls -lrt pg_xlog":
-rw--- 1 postgres postgres 16777216 May 21 12:13 0001
15 matches
Mail list logo
