On Sat, Nov 25, 2017 at 05:45:59PM -0500, Tom Lane wrote:
> Justin Pryzby writes:
> > We never had any issue during the ~2 years running PG96 on this VM, until
> > upgrading Monday to PG10.1, and we've now hit it 5+ times.
>
> > BTW this is a VM run on a hypervisor managed by our customer:
> > DM
On 11/25/2017 12:03 PM, nikhil raj wrote:
check the roles of user I want to give user roles only select,
insert, update, execute and create database to all users Permission
those permissions can be assigned on a table by table basis, except
create database, thats a special permission. if
Justin Pryzby writes:
> We never had any issue during the ~2 years running PG96 on this VM, until
> upgrading Monday to PG10.1, and we've now hit it 5+ times.
> BTW this is a VM run on a hypervisor managed by our customer:
> DMI: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platfo
Hi
I am Nikhil currently working as a MS SQL DBA . Currently my company is
shifting from MS SQL to postgres
check the roles of user I want to give user roles only select, insert,
update, execute and create database to all users Permission
The users should not have these permission
drop databa
On 24.11.2017 12:19, Oleg Bartunov wrote:
btw, in PG 11 we expect subscription index
update test set data[age]= '30';
Out of curiosity:
Why not?
update test set data->age= 30;
It reminds me more of how to query json in PG
select data->age from test;
Cheer,
Sven
On Fri, 2017-11-24 at 11:58 -0800, John R Pierce wrote:
> On 11/24/2017 11:43 AM, Michael Nolan wrote:
> > There are so many different levels of caching going on--within
> > Postgresql, within the OS, within a disk array or SAN, and at the
> > individual drive--that there may no longer be a meani
