Re: [GENERAL] journaling / time travel

Coming late to this, but ... On Mon, 19 Sep 2016 17:48:20 +0200, Willy-Bas Loos wrote: >The use case of legal disputes being fought with our data as evidence and >digging up the exact data from a certain point of time never occurred in >those 10 years, and it is unlikely

Re: [GENERAL] 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2

El 02/09/16 a las 18:28, Scott Marlowe escribió: On Thu, Sep 1, 2016 at 8:48 PM, Patrick B wrote: Why not just subscribe to another cluster on the master, then sub the slaves to that, then switchover to the new cluster on the master? Maybe he doesn't know how to

Re: [GENERAL] 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2

On 9/12/16 3:24 PM, Jeff Janes wrote: The man page you quote seems clear to me that setting it to 1, rather than leaving it at 0, makes the opportunity for corruption wider, not narrower. Yeah, I actually read it backwards. :/ I don't see how --modify-window is helpful at all here; you need

Re: [GENERAL] jsonb_set for nested new item?

> On Sep 23, 2016 5:12 PM, "Vitaly Burovoy" wrote: > On 9/23/16, Deven Phillips wrote: >> On Fri, Sep 23, 2016 at 10:14 AM, Deven Phillips >> wrote: >>> Is there a way to set a nested element for which the parent

Re: [GENERAL] jsonb_set for nested new item?

Please note that only the first case is not supported in jsonb_set(), which was a very important addition to PostgreSQL 9.5. If this case would be added, a simple call with the same path '{boo,baz}' and '"newvalue"' would always be sufficient. Goal: first path level (boo) does not exist, create

Re: [GENERAL] jsonb_set for nested new item?

Am 23.09.16 um 16:14 schrieb Deven Phillips: > Is there a way to set a nested element for which the parent paths do not > yet exist? > > For example, if I have a JSONB value called 'data': > > { > "foo": "bar" > } > > and run > > jsonb_set(data, {'boo', 'baz'}, 'newvalue') > > I would expect