Re: Mixed Locales and Upgrading

Adrian Klaver writes: > On 4/29/20 1:10 PM, Don Seiler wrote: >> On Tue, Apr 7, 2020 at 11:41 AM Don Seiler > > wrote: >> Since I'm not changing the postgres or template0 databases (leaving >> those as en_US/LATIN1), do I keep lc_collate/lc_ctype as en_US? It's >> just the

Re: Mixed Locales and Upgrading

On 4/29/20 1:10 PM, Don Seiler wrote: On Tue, Apr 7, 2020 at 11:41 AM Don Seiler > wrote: Follow-up question, the locale setting on the host would still be set to en_US (as would the postgres and template0 databases). Should I look to change that locale on the

Re: Mixed Locales and Upgrading

On Tue, Apr 7, 2020 at 11:41 AM Don Seiler wrote: > > Follow-up question, the locale setting on the host would still be set to > en_US (as would the postgres and template0 databases). Should I look to > change that locale on the system to en_US.UTF-8, or even just for the > postgres user that the

Re: Why is a check constraint not working ?

On Wed, Apr 29, 2020 at 8:17 AM David Gauthier wrote: > > Check constraints: > "dvm_events_status_check" CHECK (status::text = ANY > (ARRAY['passed'::character varying, 'failed'::character varying, > NULL::character varying]::text[])) > > > What could cause this ? > NULL in the array. "stat

Why is a check constraint not working ?

psql (9.6.7, server 11.3) I have a table... dvdb=# \d+ dvm_events; Table "dvm.dvm_events" Column | Type | Modifiers | Storage | Stats target | Description --+--+---+-

Regarding db performance improvement

Hi to PGDG TEAM kernel.shmmax=18446744073692774399 kernel.shmall=18446744073692774399 I am using linux ubuntu server(16.04) to manage pgsql. So kernel default value for kernel.shmax was 18446744073692774399 & kernel default value for kernel.shmall was 18446744073692774399 I am using postgres