Re: [GENERAL] long transfer time for binary data

On Wed, 20 Jan 2016 22:29:07 +0100, Johannes wrote: >I noticed transferring a large object or bytea data between client and >server takes a long time. >For example: An image with a real size of 11 MB could be read on server >side (explain analyze) in 81ms. Fine. > >But on client side the result w

[GENERAL] Variable not found

Dear Folks, I have a question about global variables in Oracle pl/sql package. Where are these variables when package is converted to schema from Oracle to Postgres through Ora2PG Tool? For example, package

Re: [GENERAL] adding a bdr node using bcv backup

On 21 January 2016 at 08:29, (Daniel Stolf) wrote: > Hello there... > > I'm new to postgres and I'm trying out BDR replication... > > I know that when I issue the bdr.bdr_group_join command, it will copy the > entire database from the host I specify on parameter 'join_using_dsn' and > this may ta

Re: [GENERAL] long transfer time for binary data

On 01/20/2016 03:29 PM, Johannes wrote: I noticed transferring a large object or bytea data between client and server takes a long time. For example: An image with a real size of 11 MB could be read on server side (explain analyze) in 81ms. Fine. But on client side the result was completed after

[GENERAL] adding a bdr node using bcv backup

Hello there... I'm new to postgres and I'm trying out BDR replication... I know that when I issue the bdr.bdr_group_join command, it will copy the entire database from the host I specify on parameter 'join_using_dsn' and this may take a while depending on the network and the size of the database.

Re: [GENERAL] How to stop autovacuum for daily partition old tables

> On Jan 20, 2016, at 19:54, AI Rumman wrote: > > But, will it not create transaction wraparound for those table? > > Thanks. > >> On Wed, Jan 20, 2016 at 4:44 PM, Melvin Davidson >> wrote: >> >> ALTER TABLE your_schema.your_table SET (autovacuum_enabled = false, >> toast.autovacuum_enabl

Re: [GENERAL] How to stop autovacuum for daily partition old tables

On 01/20/2016 04:54 PM, AI Rumman wrote: But, will it not create transaction wraparound for those table? See below for complete details: http://www.postgresql.org/docs/9.1/interactive/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND but short version from above: 23.1.4. Preventing Transaction I

Re: [GENERAL] How to stop autovacuum for daily partition old tables

You can only get a transaction wraparound if you actually do transactions (insert/update/delete) on a table. Since YOU claim you are not doing that, then you should not get a transaction wraparound for that table. On Wed, Jan 20, 2016 at 7:54 PM, AI Rumman wrote: > But, will it not create trans

Re: [GENERAL] How to stop autovacuum for daily partition old tables

But, will it not create transaction wraparound for those table? Thanks. On Wed, Jan 20, 2016 at 4:44 PM, Melvin Davidson wrote: > > ALTER TABLE your_schema.your_table SET (autovacuum_enabled = false, > toast.autovacuum_enabled = false); > > On Wed, Jan 20, 2016 at 6:22 PM, AI Rumman wrote: > >

Re: [GENERAL] How to stop autovacuum for daily partition old tables

ALTER TABLE your_schema.your_table SET (autovacuum_enabled = false, toast.autovacuum_enabled = false); On Wed, Jan 20, 2016 at 6:22 PM, AI Rumman wrote: > Hi, > > I have a table with daily partition schema on Postgresql 9.1 where we are > keeping 2 years of data. > Often I experience that autova

[GENERAL] adding a bdr node using bcv backup

Hello there... I'm new to postgres and I'm trying out BDR replication... I know that when I issue the bdr.bdr_group_join command, it will copy the entire database from the host I specify on parameter 'join_using_dsn' and this may take a while depending on the network and the size of the database.

[GENERAL] How to stop autovacuum for daily partition old tables

Hi, I have a table with daily partition schema on Postgresql 9.1 where we are keeping 2 years of data. Often I experience that autovacuum process is busy with old tables where there is no change. How can I stop it? Please advice. Thanks.

[GENERAL] long transfer time for binary data

I noticed transferring a large object or bytea data between client and server takes a long time. For example: An image with a real size of 11 MB could be read on server side (explain analyze) in 81ms. Fine. But on client side the result was completed after 6.7 seconds without ssl compression and 4

Re: [GENERAL] CoC [Final]

Joshua D. Drake wrote: > == PostgreSQL Community Code of Conduct (CoC) == > > This document provides community guidelines for a safe, respectful, > productive, and collaborative place for any person who is willing to > contribute to the PostgreSQL community. It applies to all "collaborative > spa

Re: [GENERAL] Why PG uses nested-loop join when no indexes are available?

Thank you both for your help. We will test your patch but we need to understand a bit more the code in order to follow your discussions. Actually, your patch helps us to find where to start in the code ;). > The planner is never going to get it right 100% of the time. Yes, I agree. In production

Re: [GENERAL] Postgres and timezones

On 01/20/2016 04:24 PM, Steve Rogerson wrote: >> Postgres doesn't store original TZ. It does recalculation to local TZ. If you >> need original TZ, you have to store it separetely. >> > > I know and that's what I'm trying to deal with. Given I know the origin TZ - > as in Europe/Lisbon I'm trying

Re: [GENERAL] CoC [Final]

On 20 January 2016 at 19:14, Karsten Hilbert wrote: > On Wed, Jan 20, 2016 at 01:05:15PM -0600, Kevin Grittner wrote: > > >>> * When interpreting the words and actions of others, participants > >>> should always assume good intentions. > ... > > That came about because of the point made by someon

Re: [GENERAL] CoC [Final]

On 20 January 2016 at 19:05, Kevin Grittner wrote: > On Wed, Jan 20, 2016 at 12:47 PM, Simon Riggs > wrote: > > On 18 January 2016 at 18:02, Joshua D. Drake > wrote: > > >> * We are tolerant of people’s right to have opposing views. > >> > >> * Participants must ensure that their language and a

Re: [GENERAL] CoC [Final]

On Wed, Jan 20, 2016 at 01:05:15PM -0600, Kevin Grittner wrote: >>> * When interpreting the words and actions of others, participants >>> should always assume good intentions. ... > That came about because of the point made by someone for whom > English is a second language, who attempted to compl

Re: [GENERAL] CoC [Final]

On Wed, Jan 20, 2016 at 12:47 PM, Simon Riggs wrote: > On 18 January 2016 at 18:02, Joshua D. Drake wrote: >> * We are tolerant of people’s right to have opposing views. >> >> * Participants must ensure that their language and actions are free >> of personal attacks and disparaging personal rema

Re: [GENERAL] BDR with postgres 9.5

On 01/20/2016 11:41 AM, Nikhil wrote: > Hello All, > > > What is the timeline for BDR with postgres 9.5 released version. Currently there are no plans for BDR with 9.5. https://github.com/2ndQuadrant/bdr/issues/157#issuecomment-172402366 -- Vik Fearing +

Re: [GENERAL] CoC [Final]

On 18 January 2016 at 18:02, Joshua D. Drake wrote: > O.k. so I let every thing sit with V7 for several days and we have > received no further feedback. I believe we have reached a point where we > can reasonably consider this Final or at least Final Draft. > > This final draft incorporates all

Re: [GENERAL] CoC [Final]

On 20 January 2016 at 15:19, Brian Dunavant wrote: >> * Participants who disrupt the collaborative space, or participate in >> a pattern of behaviour which could be considered harassment will not >> be tolerated. > > Perhaps changing the ", or participate" to " by engaging" would make > that state

Re: [GENERAL] Syntax error for Function

On 01/20/2016 08:00 AM, Sachin Srivastava wrote: Dear Adiran, Thanks for your help !! First I want to say it's not giving the error for this ""languaget...@repos.birchstreet.net ", so there is any need to do the change as suggested by you. You are no

Re: [GENERAL] Postgres and timezones

On 20/01/16 15:38, Steve Crawford wrote: > Is this of any use? > > select * from pg_timezone_names where name = 'Europe/Lisbon'; > name | abbrev | utc_offset | is_dst > ---+++ > Europe/Lisbon | WET| 00:00:00 | f > A bit - but what's missing

Re: [GENERAL] Postgres and timezones

Right, I was just mentioning the existence of that built-in data in case it was of use to the OP. But I should have also mentioned some caveats in case it is important to his use-case: 1. Full names are not as standardized as one might like so there are multiple possible full names for a time zone

Re: [GENERAL] Syntax error for Function

Dear Adiran, Thanks for your help !! First I want to say it's not giving the error for this "" languaget...@repos.birchstreet.net", so there is any need to do the change as suggested by you. Second you suggested " exit with cur1; " - *You are right after putting the semi column my code is workin

Re: [GENERAL] Postgres and timezones

Hi 2016-01-20 16:24 GMT+01:00 Steve Rogerson : > On 20/01/16 13:27, Pavel Stehule wrote: > > > > > > > > Postgres doesn't store original TZ. It does recalculation to local TZ. > If you > > need original TZ, you have to store it separetely. > > > > I know and that's what I'm trying to deal with. G

Re: [GENERAL] Postgres and timezones

2016-01-20 16:38 GMT+01:00 Steve Crawford : > Is this of any use? > > select * from pg_timezone_names where name = 'Europe/Lisbon'; > name | abbrev | utc_offset | is_dst > ---+++ > Europe/Lisbon | WET| 00:00:00 | f > > This is list of know tim

Re: [GENERAL] Postgres and timezones

Is this of any use? select * from pg_timezone_names where name = 'Europe/Lisbon'; name | abbrev | utc_offset | is_dst ---+++ Europe/Lisbon | WET| 00:00:00 | f -Steve On Wed, Jan 20, 2016 at 7:24 AM, Steve Rogerson wrote: > On 20/01/16 13:2

Re: [GENERAL] Postgres and timezones

On 20/01/16 13:27, Pavel Stehule wrote: > > > > Postgres doesn't store original TZ. It does recalculation to local TZ. If you > need original TZ, you have to store it separetely. > I know and that's what I'm trying to deal with. Given I know the origin TZ - as in Europe/Lisbon I'm trying to de

Re: [GENERAL] CoC [Final]

> * Participants who disrupt the collaborative space, or participate in > a pattern of behaviour which could be considered harassment will not > be tolerated. Perhaps changing the ", or participate" to " by engaging" would make that statement more focused. > "Disrupting the collaborative space" i

Re: [GENERAL] Syntax error for Function

On 01/20/2016 06:32 AM, Sachin Srivastava wrote: Dear Thom, Please find the complete code as below and suggest now. I would suggest spending some time here: http://www.postgresql.org/docs/9.4/interactive/plpgsql.html in particular: http://www.postgresql.org/docs/9.4/interactive/plpgsql-cont

Re: [GENERAL] Syntax error for Function

Dear Thom, Please find the complete code as below and suggest now. -- -- Function: gen_budget_for_next_year(bigint, bigint, bigint) -- DROP FUNCTION gen_budget_for_next_year(bigint, bigint, bigint); CREATE OR REPLACE FUNCTION gen_budget_for_next_year( subid bigint, co

Re: [GENERAL] Error in Update and Set statement

I believe the following will do what you want. WITH poupd AS (SELECT LINE_STATUS, LINE_TYPE, PROMISE_DATE, LEAD_TIME, ITEM_NUMBER, ORDER_UOM_CODE, ORDER_QTY FROM ppo_master_detail ponum, supplierdetail sd WHERE ponum.subscriber_id = 65

Re: [GENERAL] Postgres and timezones

2016-01-20 12:10 GMT+01:00 Steve Rogerson : > Hi, this is wrong: > > # select to_char('2016-01-20 00:00'::timestamp at time zone > 'Europe/Lisbon', > 'TZ'); > to_char > - > GMT > (1 row) > > > It should be WET, "Western European Time". Is there something I'm doing > wrong? > > Actually y

Re: [GENERAL] Postgres and timezones

2016-01-20 14:24 GMT+01:00 Steve Rogerson : > On 20/01/16 12:53, Albe Laurenz wrote: > > Steve Rogerson wrote: > >> Hi, this is wrong: > >> > >> # select to_char('2016-01-20 00:00'::timestamp at time zone > 'Europe/Lisbon', > >> 'TZ'); > >> to_char > >> - > >> GMT > >> (1 row) > >> > >>

Re: [GENERAL] Postgres and timezones

On 20/01/16 12:53, Albe Laurenz wrote: > Steve Rogerson wrote: >> Hi, this is wrong: >> >> # select to_char('2016-01-20 00:00'::timestamp at time zone 'Europe/Lisbon', >> 'TZ'); >> to_char >> - >> GMT >> (1 row) >> >> >> It should be WET, "Western European Time". Is there something I'm do

Re: [GENERAL] Postgres and timezones

Steve Rogerson wrote: > Hi, this is wrong: > > # select to_char('2016-01-20 00:00'::timestamp at time zone 'Europe/Lisbon', > 'TZ'); > to_char > - > GMT > (1 row) > > > It should be WET, "Western European Time". Is there something I'm doing wrong? That query will always give you your

Re: [GENERAL] Syntax error for Function

On 20 January 2016 at 12:15, Sachin Srivastava wrote: > I am unable to find out the syntax error in below code, please suggest? > > > > ERROR: syntax error at or near "select" > LINE 44: select Count(0) into sFound from budget_period ... > ^ > ** Error **

Re: [GENERAL] JSONB performance enhancement for 9.6

On Tue, 19 Jan 2016 23:53:19 -0300 Alvaro Herrera wrote: > Bill Moran wrote: > > > As far as a current solution: my solution would be to decompose the > > JSON into an optimized table. I.e.: > > > > CREATE TABLE store1 ( > > id SERIAL PRIMARY KEY, > > data JSONB > > ); > > > > CREATE TABLE s

[GENERAL] Syntax error for Function

I am unable to find out the syntax error in below code, please suggest? ERROR: syntax error at or near "select" LINE 44: select Count(0) into sFound from budget_period ... ^ ** Error ** ERROR: syntax error at or near "select" SQL state: 42601 Ch

Re: [GENERAL] ERROR for '@' for function

Thanks Thomas !!! Now, it's working fine. On Wed, Jan 20, 2016 at 5:18 PM, Thomas Kellerer wrote: > Sachin Srivastava schrieb am 20.01.2016 um 12:42: > > How to handle this below situation, I am getting error for function, my > Postgres version is 9.4 > > is > > > > ERROR: syntax error at or

Re: [GENERAL] ERROR for '@' for function

Sachin Srivastava schrieb am 20.01.2016 um 12:42: > How to handle this below situation, I am getting error for function, my > Postgres version is 9.4 > is > > ERROR: syntax error at or near "@" > LINE 67: autonumbersett...@repos.birchstreet.net >

[GENERAL] ERROR for '@' for function

How to handle this below situation, I am getting error for function, my Postgres version is 9.4 is ERROR: syntax error at or near "@" LINE 67: autonumbersett...@repos.birchstreet.net ^ ** Error ** ERROR: syntax error at or near "@" SQL state: 42601 C

[GENERAL] Postgres and timezones

Hi, this is wrong: # select to_char('2016-01-20 00:00'::timestamp at time zone 'Europe/Lisbon', 'TZ'); to_char - GMT (1 row) It should be WET, "Western European Time". Is there something I'm doing wrong? Steve -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) T

Re: [GENERAL] Error in Update and Set statement

Hi 2016-01-20 11:45 GMT+01:00 Sachin Srivastava : > Boss !! > > I am using postgres 9.4, so how to handle this. > > I don't know Ora2Pg - try to find some option to generate in old format - or manually rewrite to supported syntax UPDATE tab SET a = x.a, ... FROM x Regards Pavel

Re: [GENERAL] Error in Update and Set statement

Boss !! I am using postgres 9.4, so how to handle this. On Wed, Jan 20, 2016 at 4:11 PM, Pavel Stehule wrote: > Hi > > 2016-01-20 11:36 GMT+01:00 Sachin Srivastava : > >> Dear Folks, >> >> How to handle the below error, please suggest. I have migrated my >> database from oracle to postgres thro

[GENERAL] BDR with postgres 9.5

Hello All, What is the timeline for BDR with postgres 9.5 released version. Best Regards, Nikhil

Re: [GENERAL] Error in Update and Set statement

Hi 2016-01-20 11:36 GMT+01:00 Sachin Srivastava : > Dear Folks, > > How to handle the below error, please suggest. I have migrated my database > from oracle to postgres through Ora2PG then I am getting this error for > function. > > If I am writing the code for every column which are within set (

Re: [GENERAL] JSONB performance enhancement for 9.6

Is there any database that actually supports what the original poster wanted ? The only thing that I know that's similar is bigtable/hbase/hypertable wide column store. The way it works is: break the lexicographically sorted rows into blocks of compressed XXKB, and then keeps an index on the start

[GENERAL] Error in Update and Set statement

Dear Folks, How to handle the below error, please suggest. I have migrated my database from oracle to postgres through Ora2PG then I am getting this error for function. If I am writing the code for every column which are within set (column name1, column name2, etc) then it's running successfully

Re: [GENERAL] JSONB performance enhancement for 9.6

On Wed, Jan 20, 2016 at 4:51 AM, Bruce Momjian wrote: > On Mon, Jan 11, 2016 at 09:01:03PM -0500, Tom Smith wrote: > > Hi, > > > > Congrats on the official release of 9.5 > > > > And I'd like bring up the issue again about if 9.6 would address the > jsonb > > performance issue > > with large numb