Re: PG12 autovac issues

On Fri, Mar 27, 2020 at 05:10:03PM -0500, Justin King wrote: > Sounds great. I will email you directly with a link! Thanks. From the logs, the infinite loop on which autovacuum jobs are stuck is clear. We have a repetitive number of anti-wraparound and non-aggressive jobs happening for 7 shared

Re: PG12 autovac issues

On Fri, Mar 27, 2020 at 08:23:03PM +0100, Julien Rouhaud wrote: > FTR we reached the 200M transaxtion earlier, and I can see multiple logs of > the > form "automatic vacuum to prevent wraparound", so non-aggressive > antiwraparound > autovacuum, all on shared relations. Thanks Julien for sharing

Re: \COPY to accept non UTF-8 chars in CHAR columns

El día sábado, marzo 28, 2020 a las 09:40:30a. m. +1300, Thomas Munro escribió: > On Sat, Mar 28, 2020 at 4:46 AM Tom Lane wrote: > > Matthias Apitz writes: > > > In short, it there a way to let \COPY accept such broken ISO bytes, just > > > complaining about, but not stopping the insert of the

PostegreSQL 9.2 to 9.6

Hi guys. We need to upgrade (asap) our PostgreSQL 9.2 cluster. We run our cluster on AWS EC2 instances, and want to upgrade to RDS 9.6. Once in RDS, it makes easier for us to major upgrade to 11. Since this upgrade must be done with minimal downtime, my original idea was to use Bucardo

Re: \COPY to accept non UTF-8 chars in CHAR columns

> "Matthias" == Matthias Apitz writes: Matthias> i.e. 0xc3 is translated to 0xc383 and the 2nd half, the Matthias> 0xbc to 0xc2bc, both translations have nothing to do with Matthias> the original split 0xc3bc, and perhaps in this case it Matthias> would be better to spill out a bl

Postgres 12 backup in 32 bit windows client

Hi! Postgres 12 is installed in Debian 10 server. Client computer is running 32 bit windows. pg_dump.exe which can downloaded as part of Postgres 12 windows installation is only 64 bit version. How to make backup from Postgres 12 in 32 bit Microsoft windows computer ? psqlodbc is used for da

Re: Postgres 12 backup in 32 bit windows client

On 3/28/20 8:18 AM, Andrus wrote: Hi! Postgres 12 is installed in Debian 10 server. Client computer is running 32 bit windows. pg_dump.exe which can downloaded as part of Postgres 12 windows installation is only 64 bit version. How to make backup from Postgres 12  in 32 bit Microsoft windows

Re: PostegreSQL 9.2 to 9.6

Hi Lucas I've made it, from 9.2 to 12.2 using slony and it worked very well :) Enrico Il sab 28 mar 2020, 13:29 Lucas Possamai ha scritto: > Hi guys. > > We need to upgrade (asap) our PostgreSQL 9.2 cluster. We run our cluster > on AWS EC2 instances, and want to upgrade to RDS 9.6. Once in RDS

Re: Postgres 12 backup in 32 bit windows client

Hi! What are you going to do with this backup? If server disk crashes, it can used to restore data. Do you have shell access to the Debian machine in order to do the backup there? I have but my application user in 32bit windows does not have. I want to allow 32 bit windows user to make bac

Re: Postgres 12 backup in 32 bit windows client

On 3/28/20 12:57 PM, Andrus wrote: Hi! What are you going to do with this backup? If server disk crashes, it can used to restore data. Do you have shell access to the Debian machine in order to do the backup there? I have but my application user in 32bit windows does not have. I want to a

Re: PG12 autovac issues

Hi, On 2020-03-28 17:47:19 +0900, Michael Paquier wrote: > On Fri, Mar 27, 2020 at 05:10:03PM -0500, Justin King wrote: > > This is encouraging. As I mentioned, we have a workaround in place for > > the moment, but don't hesitate if you need anything else from me. > > Thanks for jumping in on the

could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore

Hi! Postgres 12 database dump is created in Debian 10 using pg_dump . Trying to restore it in Windows 10 using pg_restore --clean --create --if-exists --dbname=postgres --jobs=8 --no-password mydb.backup produces strange message pg_restore: WARNING: could not determine encoding for locale

Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore

On 3/28/20 2:39 PM, Andrus wrote: Hi! Postgres 12 database dump is created in Debian 10 using pg_dump . Trying to restore it in Windows 10  using pg_restore --clean --create --if-exists --dbname=postgres --jobs=8 --no-password mydb.backup produces strange message pg_restore: WARNING:  coul

Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore

Hi! In the Debian Postgres instance in psql what does \l show for the databases? #psql namm postgres psql (12.2 (Debian 12.2-2.pgdg100+1)) Type "help" for help. namm=# \l namm List of databases Name | Owner| Encoding | Collate |Ctype| Acc

Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore

On 3/28/20 3:31 PM, Andrus wrote: Hi! In the Debian Postgres instance in psql what does \l show for the databases? #psql namm postgres psql (12.2 (Debian 12.2-2.pgdg100+1)) Type "help" for help. namm=# \l namm List of databases Name |   Owner    | Encoding |

Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore

"Andrus" writes: > Postgres 12 database dump is created in Debian 10 using pg_dump . > Trying to restore it in Windows 10 using > pg_restore --clean --create --if-exists --dbname=postgres --jobs=8 > --no-password > mydb.backup > produces strange message > pg_restore: WARNING: could not determi

Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore

I wrote: > (I do agree that that message isn't the most helpful thing. It looks > like chklocale.c is overoptimistically assuming that what it's handed > is valid, even if GetLocaleInfoEx says it isn't.) After further digging, that optimism isn't *completely* without foundation; it seems to be ba