Re: upgrade and migrate

On Wed, 2019-12-04 at 13:48 +0900, Michael Paquier wrote: > On Tue, Dec 03, 2019 at 10:32:22PM +, Julie Nishimura wrote: > > Hello, what is the best way to migrate from PostgreSQL 8.3.11 on > > x86_64-redhat-linux-gnu to PostgreSQL 9.6.16 on x86_64-pc-linux-gnu > > server, with minimal

Re: upgrade and migrate

Michael Paquier schrieb am 04.12.2019 um 05:48: > On Tue, Dec 03, 2019 at 10:32:22PM +, Julie Nishimura wrote: >> Hello, what is the best way to migrate from PostgreSQL 8.3.11 on >> x86_64-redhat-linux-gnu to PostgreSQL 9.6.16 on x86_64-pc-linux-gnu >> server, with minimal downtime? >> The

Re: upgrade and migrate

On 12/3/19 10:48 PM, Michael Paquier wrote: On Tue, Dec 03, 2019 at 10:32:22PM +, Julie Nishimura wrote: Hello, what is the best way to migrate from PostgreSQL 8.3.11 on x86_64-redhat-linux-gnu to PostgreSQL 9.6.16 on x86_64-pc-linux-gnu server, with minimal downtime? The caveat is the

Re: upgrade and migrate

On Tue, Dec 03, 2019 at 10:32:22PM +, Julie Nishimura wrote: > Hello, what is the best way to migrate from PostgreSQL 8.3.11 on > x86_64-redhat-linux-gnu to PostgreSQL 9.6.16 on x86_64-pc-linux-gnu > server, with minimal downtime? > The caveat is the source has about 80 databases overall

Re: pg_basebackup + incremental base backups

Greetings, * Christopher Pereira (krip...@imatronix.cl) wrote: > Our stream replication slave server got out of sync so we need to base > backup again. If you do WAL archiving instead of depending on the WAL to exist on the primary then a replica can catch up using WAL. Having a WAL archive

upgrade and migrate

Hello, what is the best way to migrate from PostgreSQL 8.3.11 on x86_64-redhat-linux-gnu to PostgreSQL 9.6.16 on x86_64-pc-linux-gnu server, with minimal downtime? The caveat is the source has about 80 databases overall almost 30 TB. I could migrate the smallest ones (up to 1 tb) using pg_dump

Re: Issue upgrading from V11 to V12 on Debian

On Tue, Dec 03, 2019 at 11:35:40AM -0800, Adrian Klaver wrote: > On 12/3/19 9:51 AM, stan wrote: > > > > On Tue, Dec 03, 2019 at 08:58:58AM -0800, Paul Jungwirth wrote: > > > On 12/3/19 8:46 AM, stan wrote:> So, I have V12 running as the default on > > > the machine I am testing this on > > > >

Re: Syntax error for UPDATE ... RETURNING INTO STRICT

On 12/3/19 8:24 AM, Alexander Farber wrote: Thanks for your replies! Tom has hinted that STRICT is pl/pgSQL syntax and not SQL I finally read the full function and see you declared the LANGUAGE as sql. Now things make sense:) Regards Alex -- Adrian Klaver adrian.kla...@aklaver.com

Re: Issue upgrading from V11 to V12 on Debian

stan wrote: > BUT, I went to the directory where I have the exentsion's source, did a > make clean ; make ; make install, and the files were still installed in the > V11 tree. How can I instruct the system to put these in the V12 tree? With the Debian packaging, /usr/bin/pg_config is a

Re: Issue upgrading from V11 to V12 on Debian

On Tue, Dec 03, 2019 at 08:58:58AM -0800, Paul Jungwirth wrote: > On 12/3/19 8:46 AM, stan wrote:> So, I have V12 running as the default on > the machine I am testing this on > > now: > > > > Ver Cluster Port Status OwnerData directory Log file > > 11 main5433 down

Re: Issue upgrading from V11 to V12 on Debian

On 12/3/19 9:41 AM, stan wrote: Well, this gets more interesting. I decided to try the reinstall thing agai, so I did an apt-get purge on the V12 server, started the V11 server (admiitely I did not check to see what port it started on), reinstalled the V1 package, and now BOTH are running, with

Re: Issue upgrading from V11 to V12 on Debian

On Tue, Dec 03, 2019 at 08:58:58AM -0800, Paul Jungwirth wrote: > On 12/3/19 8:46 AM, stan wrote:> So, I have V12 running as the default on > the machine I am testing this on > > now: > > > > Ver Cluster Port Status OwnerData directory Log file > > 11 main5433 down

Re: Issue upgrading from V11 to V12 on Debian

On Tue, Dec 03, 2019 at 08:58:58AM -0800, Paul Jungwirth wrote: > On 12/3/19 8:46 AM, stan wrote:> So, I have V12 running as the default on > the machine I am testing this on > > now: > > > > Ver Cluster Port Status OwnerData directory Log file > > 11 main5433 down

Re: Issue upgrading from V11 to V12 on Debian

On 12/3/19 8:46 AM, stan wrote:> So, I have V12 running as the default on the machine I am testing this on now: Ver Cluster Port Status OwnerData directory Log file 11 main5433 down postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11-main.log 12 main

Re: Issue upgrading from V11 to V12 on Debian

On Tue, Dec 03, 2019 at 11:13:55AM -0500, Tom Lane wrote: > stan writes: > > I am working on upgrading from V11 to V12 on Debian. > > My first attempt failed, and I have figured out that this is because I have > > added extensions to the V11 DB, at least one of which was not installed > > using

Re: Syntax error for UPDATE ... RETURNING INTO STRICT

Thanks for your replies! Tom has hinted that STRICT is pl/pgSQL syntax and not SQL Regards Alex >

Re: Issue upgrading from V11 to V12 on Debian

On 12/3/19 7:53 AM, stan wrote: I am working on upgrading from V11 to V12 on Debian. My first attempt failed, and I have figured out that this is because I have added extensions to the V11 DB, at least one of which was not installed using the Debian packages. So, it looks like i need to

Re: Issue upgrading from V11 to V12 on Debian

stan writes: > I am working on upgrading from V11 to V12 on Debian. > My first attempt failed, and I have figured out that this is because I have > added extensions to the V11 DB, at least one of which was not installed > using the Debian packages. > So, it looks like i need to install these

Issue upgrading from V11 to V12 on Debian

I am working on upgrading from V11 to V12 on Debian. My first attempt failed, and I have figured out that this is because I have added extensions to the V11 DB, at least one of which was not installed using the Debian packages. So, it looks like i need to install these before doing the upgrade,

Re: Syntax error for UPDATE ... RETURNING INTO STRICT

On 12/3/19 3:37 AM, Alexander Farber wrote: Thank you Patrick - On Tue, Dec 3, 2019 at 11:49 AM Patrick FICHE > wrote: It seems that STRICT is the issue. But why does your function return a table of boolean in this case ? As it only

Re: Syntax error for UPDATE ... RETURNING INTO STRICT

Alexander Farber writes: > why does not PostgreSQL 10.11 please like the - I think you are confusing plpgsql syntax with sql syntax. regards, tom lane

Re: slow insert speeds with bytea

On Mon, Dec 2, 2019 at 4:42 AM Alex O'Ree wrote: > Is there anything I can to increase insert speeds for bytea? Currently > running postgres 9.6.15 > > I have a few tables without a bytea and a few with bytea. There is a large > performance difference with inserts between the two. I'm inserting

Re: Syntax error for UPDATE ... RETURNING INTO STRICT

Thank you Patrick - On Tue, Dec 3, 2019 at 11:49 AM Patrick FICHE wrote: > > It seems that STRICT is the issue. > > But why does your function return a table of boolean in this case ? > > As it only updates one record, it would probably be easier to return a > boolean only. > > CREATE OR

RE: Syntax error for UPDATE ... RETURNING INTO STRICT

Hi Alexander, It seems that STRICT is the issue. But why does your function return a table of boolean in this case ? As it only updates one record, it would probably be easier to return a boolean only. CREATE OR REPLACE FUNCTION words_toggle_puzzle( in_mid bigint )

Syntax error for UPDATE ... RETURNING INTO STRICT

Good morning, why does not PostgreSQL 10.11 please like the - CREATE OR REPLACE FUNCTION words_toggle_puzzle( in_mid bigint ) RETURNS table ( out_puzzle boolean ) AS $func$ UPDATE words_moves SET puzzle = NOT puzzle