On 16 August 2017 at 20:55, Achilleas Mantzios wrote:
> On 16/08/2017 13:46, Alex Samad wrote:
>
>
>
> On 16 August 2017 at 16:16, Michael Paquier
> wrote:
>
>> On Wed, Aug 16, 2017 at 2:32 PM, Alex Samad wrote:
>> > 1) why did it fill up this time and not previously
>> > I add this
>> > archiv
Great I will add it to my notes.
Thanks
On 16 August 2017 at 20:55, Achilleas Mantzios wrote:
> On 16/08/2017 13:46, Alex Samad wrote:
>
>
>
> On 16 August 2017 at 16:16, Michael Paquier
> wrote:
>
>> On Wed, Aug 16, 2017 at 2:32 PM, Alex Samad wrote:
>> > 1) why did it fill up this time and
On 16/08/2017 13:46, Alex Samad wrote:
On 16 August 2017 at 16:16, Michael Paquier mailto:michael.paqu...@gmail.com>> wrote:
On Wed, Aug 16, 2017 at 2:32 PM, Alex Samad mailto:a...@samad.com.au>> wrote:
> 1) why did it fill up this time and not previously
> I add this
> archive
On 16 August 2017 at 16:16, Michael Paquier
wrote:
> On Wed, Aug 16, 2017 at 2:32 PM, Alex Samad wrote:
> > 1) why did it fill up this time and not previously
> > I add this
> > archive_command = '/bin/true'
> > wal_keep_segments = 1000 # <<< I'm guessing its this
> >
> > 2) how do I fix up, can
On Wed, Aug 16, 2017 at 2:32 PM, Alex Samad wrote:
> 1) why did it fill up this time and not previously
> I add this
> archive_command = '/bin/true'
> wal_keep_segments = 1000 # <<< I'm guessing its this
>
> 2) how do I fix up, can I just remove the files from the pg_xlog directory
Don't do that.
Hi
So I have been playing with an streaming cluster. I have the replication
working I believe.
But whilst attempting to do an import of my original DB, I filled up my
disk pg_xlog directory.
Strangley I have tried this before and not filled this up.
so
1) why did it fill up this time and not p
