Re: Migrating Postgresql from Linux x86

Hi. We do that migration from Postgres 9.0 (x86_64, Centos 6) to Postgres 9.6 (power, SUSE Enterprise 12). The best way to us was to do a backup (pg_dump -Fc ...) and restore using several cores (pg_restore -j N ..., where N equals to the cores/jobs to be used). How many jobs launch to restore

Migrating Postgresql from Linux x86

Hi Anyone have migrated PostgreSQL running on Linux x86_64 to running on Linux on Power platform. Interested in a checklist of things to be done and if there is a proper document with the steps to completing would also be of interest. Thanks Clive A.

Re: Odd behavior with 'currval'

On Fri, 9 Feb 2018, Francisco Olarte wrote: I was trying to be careful and changed the address manually for all messages except this one. Do not bother with that. The style in this list is to just reply to all, so the people that are participating in the thread can get a copy of the messages

Re: Odd behavior with 'currval'

Adrian: On Fri, Feb 9, 2018 at 7:17 PM, Adrian Klaver wrote: > On 02/09/2018 09:43 AM, Francisco Olarte wrote: >> It's probably because this list headers are "old school", without >> those newflangled thingied. > I believe with the change to PGLister that changed:

Re: Odd behavior with 'currval'

On 02/09/2018 09:43 AM, Francisco Olarte wrote: Steven: On Fri, Feb 9, 2018 at 6:33 PM, Steven Hirsch wrote: Ah, blast... Apologies to everyone concerned. I need to understand why my mail reader (Alpine on Linux) insists on defaulting to the original poster's e-mail

Re: initdb execution

Thanks for the reply.. Let me execute in the newly built setup. On Fri, Feb 9, 2018 at 11:50 AM, Francisco Olarte wrote: > Azim > > On Fri, Feb 9, 2018 at 6:36 PM, Azimuddin Mohammed > wrote: > > Hello I have a question regrading initdb, > > My

Re: Odd behavior with 'currval'

Steven: On Fri, Feb 9, 2018 at 6:33 PM, Steven Hirsch wrote: > Ah, blast... Apologies to everyone concerned. I need to understand why my > mail reader (Alpine on Linux) insists on defaulting to the original poster's > e-mail address when I hit 'Reply' rather than the group

Re: Odd behavior with 'currval'

Steven: On Fri, Feb 9, 2018 at 5:58 PM, Steven Hirsch wrote: > On Fri, 9 Feb 2018, Francisco Olarte wrote: >> This may sound a bit harsh but: >>> The culprit is in the JDBC domain, NOT PostgreSQL! According to the >>> documentation I found, the ResultSet 'getLong()' method

initdb execution

Hello I have a question regrading initdb, My understanding of initdb is when we execute it it will create the directory structure in /data. My question is when we run initdb when we already have a database running and for some reason I run this command what happens to my existing actual data does

Re: Odd behavior with 'currval'

On Fri, 9 Feb 2018, Adrian Klaver wrote: I remember seeing it, so I went back to look at the message. Turns out you sent it to me only. Unfortunately I am not a Java programmer so I did not catch the error. For the record: Ah, blast... Apologies to everyone concerned. I need to understand

Re: Odd behavior with 'currval'

On 02/09/2018 08:58 AM, Steven Hirsch wrote: On Fri, 9 Feb 2018, Francisco Olarte wrote: This may sound a bit harsh but: The culprit is in the JDBC domain, NOT PostgreSQL!  According to the documentation I found, the ResultSet 'getLong()' method returns a value of zero when it sees NULL as

Re: Odd behavior with 'currval'

On Fri, 9 Feb 2018, Francisco Olarte wrote: This may sound a bit harsh but: The culprit is in the JDBC domain, NOT PostgreSQL! According to the documentation I found, the ResultSet 'getLong()' method returns a value of zero when it sees NULL as an input. Why the JDBC libs don't treat this as

testing for DEFAULT insert value in ON CONFLICT DO UPDATE query

Hi Is there any way to tell if a conflicting row in an multi-line INSERT used the DEFAULT directive? I would like to be able to upsert a bunch of rows and only UPDATE the conflicting rows where the value set was not new - the way I do this for NULLable columns is to just write NULL in the INSERT

Re: Odd behavior with 'currval'

On Fri, Feb 9, 2018 at 8:27 AM, Francisco Olarte wrote: > On Thu, Feb 8, 2018 at 8:12 PM, Steven Hirsch wrote: > . > > > 2. Why is the currval() function being so blasted dumb? If > > 'pg_get_serial_sequence' cannot resolve the sequence, it

Re: Odd behavior with 'currval'

On Thu, Feb 8, 2018 at 8:12 PM, Steven Hirsch wrote: . > 2. Why is the currval() function being so blasted dumb? If > 'pg_get_serial_sequence' cannot resolve the sequence, it returns NULL. As > such, shouldn't the outer currval() also be returning NULL? I cannot >