Re:Postgresql with JDK

Hi, Yes that is the link. But is JDK 1.8 supported by PostgreSQL?? Regards, Vaibhav Zaveri On 17 Apr 2018 12:12 p.m., "Mail Delivery Subsystem" < mailer-dae...@googlemail.com> wrote: [image: Error Icon] Address not found Your message wasn't delivered to *pgsl-gene...@postgresql.org* because the

RE: Which jdk version is supported by PostgreSQL

> -Original Message- > From: vaibhav zaveri > Sent: Tuesday, April 17, 2018 2:03 PM > To: pgsql-gene...@postgresql.org; pgsql_gene...@postgresql.org > Subject: Which jdk version is supported by PostgreSQL > > Hi, > > Which jdk version is supported by PostgreSQL? > > > Regards, > Vaibha

Re: To prefer sorts or filters in postgres, that is the question....

Bob Jones wrote: > I've been playing around with hierarchical queries a bit and one thing > I wanted to do is build a query that gives the ultimate parent for a > given child. > > The two queries below seem to be a good a shortlist as any. > > I'm no query-plan guru, but these seem to be largely

Which jdk version is supported by PostgreSQL

Hi, Which jdk version is supported by PostgreSQL? Regards, Vaibhav Zaveri

Re: pg_dump to a remote server

## Ron (ronljohnso...@gmail.com): > > pg_dump -h host1 dbname | psql -h host2 dbname > > But that assumes --format=plain which will send a whole lot of > uncompressed text across the wire. You can also use pg_restore with standard input, i.e. pg_dump | pg_restore. Regards, Christoph -- Spare

Re: pg_dump to a remote server

On 04/16/2018 06:43 PM, Ron wrote: On 04/16/2018 07:18 PM, Adrian Klaver wrote: On 04/16/2018 04:58 PM, Ron wrote: We're upgrading from v8.4 to 9.6 on a new VM in a different DC.  The dump file will be more than 1TB, and there's not enough disk space on the current system for the dump file.

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On Mon, Apr 16, 2018 at 2:26 PM, Adrian Klaver wrote: > On 04/16/2018 10:18 AM, Keith Fiske wrote: > >> >> >> On Mon, Apr 16, 2018 at 12:21 PM, Tom Lane > t...@sss.pgh.pa.us>> wrote: >> >> > >> So playing around with the "client_encoding" configuration option in >> postgresql.conf. According to t

Re: pg_dump to a remote server

On 04/16/2018 07:18 PM, Adrian Klaver wrote: On 04/16/2018 04:58 PM, Ron wrote: We're upgrading from v8.4 to 9.6 on a new VM in a different DC.  The dump file will be more than 1TB, and there's not enough disk space on the current system for the dump file. Thus, how can I send the pg_dump f

Re: pg_dump to a remote server

On 04/16/2018 07:47 PM, Gao Jack wrote: -Original Message- From: Ron Sent: Tuesday, April 17, 2018 7:59 AM To: pgsql-general Subject: pg_dump to a remote server We're upgrading from v8.4 to 9.6 on a new VM in a different DC.  The dump file will be more than 1TB, and there's not enough

RE: pg_dump to a remote server

> -Original Message- > From: Ron > Sent: Tuesday, April 17, 2018 7:59 AM > To: pgsql-general > Subject: pg_dump to a remote server > > We're upgrading from v8.4 to 9.6 on a new VM in a different DC.  The dump > file will be more than 1TB, and there's not enough disk space on the current

Re: pg_dump to a remote server

On Mon, Apr 16, 2018 at 6:58 PM, Ron wrote: > We're upgrading from v8.4 to 9.6 on a new VM in a different DC. The dump > file will be more than 1TB, and there's not enough disk space on the > current system for the dump file. > > Thus, how can I send the pg_dump file directly to the new server w

Re: pg_dump to a remote server

On 04/16/2018 04:58 PM, Ron wrote: We're upgrading from v8.4 to 9.6 on a new VM in a different DC.  The dump file will be more than 1TB, and there's not enough disk space on the current system for the dump file. Thus, how can I send the pg_dump file directly to the new server while the pg_dum

pg_dump to a remote server

We're upgrading from v8.4 to 9.6 on a new VM in a different DC.  The dump file will be more than 1TB, and there's not enough disk space on the current system for the dump file. Thus, how can I send the pg_dump file directly to the new server while the pg_dump command is running?  NFS is one me

To prefer sorts or filters in postgres, that is the question....

Hi, I've been playing around with hierarchical queries a bit and one thing I wanted to do is build a query that gives the ultimate parent for a given child. The two queries below seem to be a good a shortlist as any. I'm no query-plan guru, but these seem to be largely identical aside from one

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On 04/16/2018 10:18 AM, Keith Fiske wrote: On Mon, Apr 16, 2018 at 12:21 PM, Tom Lane > wrote: So playing around with the "client_encoding" configuration option in postgresql.conf. According to the docs, setting this should set the default encoding for any cli

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On 04/16/2018 10:18 AM, Keith Fiske wrote: So playing around with the "client_encoding" configuration option in postgresql.conf. According to the docs, setting this should set the default encoding for any client that connects, right? https://www.postgresql.org/docs/10/static/runtime-con

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On 04/16/2018 10:18 AM, Keith Fiske wrote: So playing around with the "client_encoding" configuration option in postgresql.conf. According to the docs, setting this should set the default encoding for any client that connects, right? For any client that does not set a client_encoding when

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On Mon, Apr 16, 2018 at 12:21 PM, Tom Lane wrote: > Keith Fiske writes: > > On Mon, Apr 16, 2018 at 12:09 PM, Tom Lane wrote: > >> This is not a great idea, no. You could be getting strange misbehaviors > >> in e.g. string comparison, because strcoll() will expect UTF8 data and > >> will likel

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On Mon, Apr 16, 2018 at 12:30 PM, Vick Khera wrote: > Hi Keith, > > Not sure if this will help but a couple of years ago I migrated from an > SQL_ASCII encoding to UTF8. The data was primarily ASCII with some windows > garbage, and a little bit of UTF8 from customers filling out forms that > were

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On Mon, Apr 16, 2018 at 12:21 PM, Tom Lane wrote: > Keith Fiske writes: > > On Mon, Apr 16, 2018 at 12:09 PM, Tom Lane wrote: > >> This is not a great idea, no. You could be getting strange misbehaviors > >> in e.g. string comparison, because strcoll() will expect UTF8 data and > >> will likel

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

Hi Keith, Not sure if this will help but a couple of years ago I migrated from an SQL_ASCII encoding to UTF8. The data was primarily ASCII with some windows garbage, and a little bit of UTF8 from customers filling out forms that were not specifically encoded anything. I wrote a utility that in-pl

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

Keith Fiske writes: > On Mon, Apr 16, 2018 at 12:09 PM, Tom Lane wrote: >> This is not a great idea, no. You could be getting strange misbehaviors >> in e.g. string comparison, because strcoll() will expect UTF8 data and >> will likely not cope well with data that isn't valid in that encoding.

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On Mon, Apr 16, 2018 at 12:09 PM, Tom Lane wrote: > Keith Fiske writes: > > Running into an issue with helping a client upgrade from 8.3 to 10 (yes, > I > > know, please keep the out of support comments to a minimum, thanks :). > > > The old database was in SQL_ASCII and it needs to stay that wa

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

Keith Fiske writes: > Running into an issue with helping a client upgrade from 8.3 to 10 (yes, I > know, please keep the out of support comments to a minimum, thanks :). > The old database was in SQL_ASCII and it needs to stay that way for now > unfortunately. The dump and restore itself works fi

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On 04/16/2018 08:16 AM, Keith Fiske wrote: Running into an issue with helping a client upgrade from 8.3 to 10 (yes, I know, please keep the out of support comments to a minimum, thanks :). The old database was in SQL_ASCII and it needs to stay that way for now unfortunately. The dump and resto

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On 04/16/2018 08:16 AM, Keith Fiske wrote: Running into an issue with helping a client upgrade from 8.3 to 10 (yes, I know, please keep the out of support comments to a minimum, thanks :). The old database was in SQL_ASCII and it needs to stay that way for now unfortunately. The dump and resto

client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

Running into an issue with helping a client upgrade from 8.3 to 10 (yes, I know, please keep the out of support comments to a minimum, thanks :). The old database was in SQL_ASCII and it needs to stay that way for now unfortunately. The dump and restore itself works fine, but we're now running int

Re: SQL statement in an error report for deferred constraint violation.

Konrad Witaszczyk wrote > Hi, > > While PQresultErrorField() from libpq allows to get context in which an > error > occurred for immediate constraints, and thus an SQL statement which caused > the > constraint violation, I cannot see any way to find out which SQL statement > caused an error in ca

Re: Data migration from postgres 8.4 to 9.4

On Mon, Apr 16, 2018 at 12:33 PM, Akshay Ballarpure < akshay.ballarp...@tcs.com> wrote: > Hello, > I need help in using postgresql 8.4 data in postgres 9.4 version. Do I > need to run any tool to achieve the same? > > Steps i followed is ran postgresql 8.4 and 9.4, copied data from 8.4 > instance