Postgres 9.4 Needed

Hi Team, I have to install Postgres 9.4 which is compatible with Jira 7.2.2 . We have to migrate the data from older version to New but before we need to restore the Data . Hence, Postgres 9.4 is needed. I do not find the 9.4 repo or postgresql94-server anywhere online as it is decommissioned

Re: Postgres 9.4 Needed

Hi Taranum, > On 09. Feb, 2021, at 01:59, Taranum Fatima wrote: > > Do you have any place from where I can download this 9.4 repository and > 94server? old versions of PostgreSQL can still be downloaded from: https://www.postgresql.org/ftp/ Cheers, Paul

Increased size of database dump even though LESS consumed storage

Hi all, for various reasons I've migrated my database schema from 4 tables with some additional indexes to keep integrity and stuff to 1 table only. That made some of the former used indexes obsolete and resulted in overall less consumed storage: The old schema consumed ~42 GiB, while the new is

Re: Postgres 9.4 Needed

Hi Taranum, > On 09. Feb, 2021, at 10:21, Taranum Fatima wrote: > > I am new to postgres, can you please guide me from which folder I can get the > downloadable and repository for 9.4? depends on what platform you're on. Windows? Linux? Solaris?... Seems like all the directories in the binary

Re: Postgres 9.4 Needed

Hi Taranum, > On 09. Feb, 2021, at 11:09, Paul Förster wrote: >> I am new to postgres, can you please guide me from which folder I can get >> the downloadable and repository for 9.4? you may also try this if you need a binary release: https://www.enterprisedb.com/downloads/postgres-postgresql-

Re: Postgres 9.4 Needed

Hi Paul Thank you for the reply I am new to postgres, can you please guide me from which folder I can get the downloadable and repository for 9.4? Get Outlook for Android From: Paul Förster Sent: Tuesday, 9 February 2021, 2:46 pm To: Tar

Re: Postgres 9.4 Needed

Taranum Fatima schrieb am 09.02.2021 um 01:59: > I have to install Postgres 9.4 which is compatible with Jira 7.2.2 .  > > We have to migrate the data from older version to New  but before we need to > restore the Data . Hence, Postgres 9.4 is needed. > > I do not find the 9.4 repo or postgresql94

How to I select value of GUC that has - in its name?

Hi, question from IRC, but I couldn't find an answer. I can set custom guc with - in name, but I can't figure out how to select it. Without minus, it works great: =$ psql -X -c 'show custom.guc' ERROR: unrecognized configuration parameter "custom.guc" =$ psql -X -c "alter user depesz set custo

Re: How to I select value of GUC that has - in its name?

On 09/02/2021 14:40, hubert depesz lubaczewski wrote: > Hi, > question from IRC, but I couldn't find an answer. > > I can set custom guc with - in name, but I can't figure out how to > select it. > > Without minus, it works great: > > =$ psql -X -c 'show custom.guc' > ERROR: unrecognized configura

Re: Increased size of database dump even though LESS consumed storage

=?utf-8?B?VGhvcnN0ZW4gU2Now7ZuaW5n?= writes: > for various reasons I've migrated my database schema from 4 tables > with some additional indexes to keep integrity and stuff to 1 table > only. That made some of the former used indexes obsolete and resulted > in overall less consumed storage: > The o

Re: How to I select value of GUC that has - in its name?

On Tue, Feb 09, 2021 at 02:49:19PM +, Edward Macnaghten wrote: > > $ alter user depesz set custom.bad-guc = '1a'; > > ERROR: syntax error at or near "-" > > LINE 1: alter user depesz set custom.bad-guc = '1a'; > Have you tried enclosing "bad-guc" in double quotes? I'm sorry, but have you read

Re: Increased size of database dump even though LESS consumed storage

Guten Tag Thorsten Schöning, am Dienstag, 9. Februar 2021 um 10:56 schrieben Sie: > Any explanation for the increased dump size? Thanks! Some more data: > --compress=0: 20 vs. 25 GiB > --compress=DEFAULT: 6,5 vs. 5,6 GiB > --compress=9: 6,4 vs. 5,5 GiB From the docs: > For the cus

Re: How to I select value of GUC that has - in its name?

On 2/9/21 6:40 AM, hubert depesz lubaczewski wrote: Hi, question from IRC, but I couldn't find an answer. I can set custom guc with - in name, but I can't figure out how to select it. Without minus, it works great: =$ psql -X -c 'show custom.guc' ERROR: unrecognized configuration parameter "c

Re: How to I select value of GUC that has - in its name?

On Tue, Feb 09, 2021 at 07:41:02AM -0800, Adrian Klaver wrote: > The only way I found so far is: > select setconfig[array_position(setconfig, 'custom.bad-guc=1a')] from > pg_db_role_setting where setrole = 'aklaver'::regrole; Yeah, but this will require some parsing if I don't know what the value

Re: How to I select value of GUC that has - in its name?

On 2/9/21 7:45 AM, hubert depesz lubaczewski wrote: On Tue, Feb 09, 2021 at 07:41:02AM -0800, Adrian Klaver wrote: The only way I found so far is: select setconfig[array_position(setconfig, 'custom.bad-guc=1a')] from pg_db_role_setting where setrole = 'aklaver'::regrole; Yeah, but this will re

How does Postgres decide if to use additional workers?

Hi all, I have the following table with an added BTREE-index on "captured_at". > CREATE TABLE datagram > ( > idbigserial NOT NULL, > src_reinteger NOT NULL, > src_clt integer NOT NULL, > src_meter integer

Re: How does Postgres decide if to use additional workers?

De: "Thorsten Schöning" Para: "pgsql-general" Enviadas: Terça-feira, 9 de fevereiro de 2021 12:52:02 Assunto: How does Postgres decide if to use additional workers? So, based on which facts does Postgres decide if to use aadditional workers or not? Can I see those decisions explained somewhe

Re: How to I select value of GUC that has - in its name?

Adrian Klaver writes: > On 2/9/21 7:45 AM, hubert depesz lubaczewski wrote: >> but I find it curious that I can set the guc using normal-ish SET, but >> can't get it using SHOW or even select current_setting() > Yeah, I think that part is a bug report. After digging around in the code, I find th

quoted-printable to jsonb

Greetings PG-users, Scenario: I am using FreeRADIUS to insert data to a PG database. One of the pieces of data is an array of key value pairs. The array is encoded with quoted-printable [0]. I'd like to ideally have the key-value pair put into a JSONB field. Here is an example of the data enco

Re: How to I select value of GUC that has - in its name?

> Sure enough, > regression=> show custom."bad-guc"; > ERROR: unrecognized configuration parameter "custom.bad-guc" > regression=> show custom."bad_guc"; > custom.bad_guc > > 1a > (1 row) > So that's where the setting went. Oh, that's interesting. Unfortuantley it can also lea

Re: How to I select value of GUC that has - in its name?

On 2/9/21 9:00 AM, Tom Lane wrote: Adrian Klaver writes: On 2/9/21 7:45 AM, hubert depesz lubaczewski wrote: but I find it curious that I can set the guc using normal-ish SET, but can't get it using SHOW or even select current_setting() Yeah, I think that part is a bug report. After diggi

psql behavior change on upgrade from version 12.x to 13.1

Using a MacBook Pro with the current Big Sur—Version 11.2 (20D64). I just upgraded to PostgreSQL 13.1. (Earlier, I was on 12.x.) Using psql, the behavior of ordinary copy-and-paste has change dramatically, and for the worse, w.r.t. Version 12. HAS ANYBODY ELSE SEEN WHAT I REPORT BELOW? First

Re: psql behavior change on upgrade from version 12.x to 13.1

Hi Bryn, > On 09. Feb, 2021, at 19:55, Bryn Llewellyn wrote: > > Using a MacBook Pro with the current Big Sur—Version 11.2 (20D64). > > I just upgraded to PostgreSQL 13.1. (Earlier, I was on 12.x.) Using psql, the > behavior of ordinary copy-and-paste has change dramatically, and for the > wo

Re: psql behavior change on upgrade from version 12.x to 13.1

paul.foers...@gmail.com wrote: Hi Bryn, > On 09. Feb, 2021, at 19:55, Bryn Llewellyn wrote: > > Using a MacBook Pro with the current Big Sur—Version 11.2 (20D64). > > I just upgraded to PostgreSQL 13.1. (Earlier, I was on 12.x.) Using psql, the > behavior of ordinary copy-and-paste has change

Re: psql behavior change on upgrade from version 12.x to 13.1

Bryn Llewellyn writes: > HAS ANYBODY ELSE SEEN WHAT I REPORT BELOW? > First observation > Now, when I copy a single line SQL command, terminated with semicolon and > newline from the Text Edit app (with Command-C or the menu item) and then > paste it into psql (with Command-V or the menu item)

Re: psql behavior change on upgrade from version 12.x to 13.1

On 09-Feb-2021, at 11:43, Tom Lane wrote: Bryn Llewellyn writes: > HAS ANYBODY ELSE SEEN WHAT I REPORT BELOW? > First observation > Now, when I copy a single line SQL command, terminated with semicolon and > newline from the Text Edit app (with Command-C or the menu item) and then > paste

Re: psql behavior change on upgrade from version 12.x to 13.1

Bryn Llewellyn writes: > Here’s what I get when I do "otool -L /usr/local/bin/psql"; > /usr/local/bin/psql: > /usr/local/lib/libpq.5.dylib (compatibility version 5.0.0, current > version 5.13.0) > /usr/local/opt/readline/lib/libreadline.8.dylib (compatibility version > 8.0.0, curren

Re: psql behavior change on upgrade from version 12.x to 13.1

On 2/9/21 1:57 PM, Bryn Llewellyn wrote: [snip] In other words, different from what you see. I'm an ordinary end user. I don't even think expllictly about “building" anything in the PostgreSQL system. I got into this mess (as I believe) because I did this: brew update brew upgrade A colleague

Re: psql behavior change on upgrade from version 12.x to 13.1

On 09-Feb-2021, at 12:11, Tom Lane wrote: Bryn Llewellyn writes: > Here’s what I get when I do "otool -L /usr/local/bin/psql"; > /usr/local/bin/psql: > /usr/local/lib/libpq.5.dylib (compatibility version 5.0.0, current > version 5.13.0) > /usr/local/opt/readline/lib/libreadline.

Re: psql behavior change on upgrade from version 12.x to 13.1

On 2/9/21 12:19 PM, Bryn Llewellyn wrote: On 09-Feb-2021, at 12:11, Tom Lane wrote: Bryn Llewellyn writes: Here’s what I get when I do "otool -L /usr/local/bin/psql"; /usr/local/bin/psql: /usr/local/lib/libpq.5.dylib (compatibility version 5.0.0, current version 5.13.0)

Re: psql behavior change on upgrade from version 12.x to 13.1

On 09-Feb-2021, at 12:49, Adrian Klaver wrote: On 2/9/21 12:19 PM, Bryn Llewellyn wrote: > On 09-Feb-2021, at 12:11, Tom Lane wrote: > Bryn Llewellyn writes: >> Here’s what I get when I do "otool -L /usr/local/bin/psql"; >> /usr/local/bin/psql: >> /usr/local/lib/libpq.5.dylib (compatibil

Re: psql behavior change on upgrade from version 12.x to 13.1

On Tue, Feb 09, 2021 at 12:19:21PM -0800, Bryn Llewellyn wrote: > > > On 09-Feb-2021, at 12:11, Tom Lane wrote: > > Bryn Llewellyn writes: > > Here’s what I get when I do "otool -L /usr/local/bin/psql"; > > > /usr/local/bin/psql: > > /usr/local/lib/libpq.5.dylib (compatibility version

Re: psql behavior change on upgrade from version 12.x to 13.1

On 09-Feb-2021, at 14:16, raf wrote: On Tue, Feb 09, 2021 at 12:19:21PM -0800, Bryn Llewellyn wrote: > > > On 09-Feb-2021, at 12:11, Tom Lane wrote: > > Bryn Llewellyn writes: >> Here’s what I get when I do "otool -L /usr/local/bin/psql"; > >> /usr/local/bin/psql: >> /usr/local/lib/