Re: Server goes to Recovery Mode when run a SQL
Nothing was change, Postgres 10, Ubuntu 16.04 and Schema was the same, before and after that problem. Well, that database is replicated and on replicated server that problem doesn´t occur. -- Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
Need details on 9.6 version of postgres
Hi, I am using Jboss EAP 6.1 version. For Database i am using the postgres 9.3 version. Can i upgrade to postgres 9.6 without any issue. I am also considering to implement BDR 2.0, please let me know how i can get the licensing details. -- with regards A H S Phanindra
Re: Need details on 9.6 version of postgres
On 2/4/19 2:10 AM, A H S Phanindra wrote: Hi, I am using Jboss EAP 6.1 version. For Database i am using the postgres 9.3 version. Can i upgrade to postgres 9.6 without any issue. I Don't know. A place you might find out: https://developer.jboss.org/en/products/eap am also considering to implement BDR 2.0, please let me know how i can get the licensing details. https://www.2ndquadrant.com/en/resources/postgres-bdr-2ndquadrant/postgres-bdr-deployment-options/ -- with regards A H S Phanindra -- Adrian Klaver adrian.kla...@aklaver.com
Re: Server goes to Recovery Mode when run a SQL
On 2/4/19 3:13 AM, PegoraroF10 wrote: Nothing was change, Postgres 10, Ubuntu 16.04 and Schema was the same, before and after that problem. Well something changed or you would not be having a problem. Well, that database is replicated and on replicated server that problem doesn´t occur. Define what you mean by replicated? -- Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html -- Adrian Klaver adrian.kla...@aklaver.com
Re: Need details on 9.6 version of postgres
Am 04.02.19 um 11:10 schrieb A H S Phanindra: Hi, I am using Jboss EAP 6.1 version. For Database i am using the postgres 9.3 version. Can i upgrade to postgres 9.6 without any issue. should work, but you should test it. I am also considering to implement BDR 2.0, please let me know how i can get the licensing details. consider BDR3, that's the current development. It works with PG 10 and 11. You need a support contract. Where are you located, i can connect you with the regional account manager, if you want. Regards, Andreas -- 2ndQuadrant - The PostgreSQL Support Company. www.2ndQuadrant.com
Re: Server goes to Recovery Mode when run a SQL
About replication ... Logical Replication with CREATE PUBLICATION/SUBSCRIPTION. Yes, some DDL commands were ran on that server but none of them were related with that select. Let me explain better. We have a single server with a single database on it. Each customer has its own schema and connects to it to work exclusively on that schema. So, sometimes we add some customer or change something on an old one. But this DDL change we could ran is not related with that schema we are talking. Schemas can have different structures but that schema which puts my server on recovery mode was not changed. Maybe something related happened some days ago. When we start a new customer we add a schema, put all their tables on it and it´s ok. Our server has today 90 schemas and each schema has 100 tables, resulting in 9000 tables. Some days ago we added 5 new customers on same day, so we added 500 tables. Then, when we did that some selects on system tables were very very slow and that was only solved when we did a REINDEX DATABASE. Even REINDEX SYSTEM did not solve. Is this problem related with recovery mode of my server ? -- Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
Re: Server goes to Recovery Mode when run a SQL
On 2/4/19 7:33 AM, PegoraroF10 wrote: About replication ... Logical Replication with CREATE PUBLICATION/SUBSCRIPTION. Yes, some DDL commands were ran on that server but none of them were related with that select. Let me explain better. We have a single server with a single database on it. Each customer has its own schema and connects to it to work exclusively on that schema. So, sometimes we add some customer or change something on an old one. But this DDL change we could ran is not related with that schema we are talking. Schemas can have different structures but that schema which puts my server on recovery mode was not changed. Maybe something related happened some days ago. When we start a new customer we add a schema, put all their tables on it and it´s ok. Our server has today 90 schemas and each schema has 100 tables, resulting in 9000 tables. Some days ago we added 5 new customers on same day, so we added 500 tables. Then, when we did that some selects on system tables were very very slow and that was only solved when we did a REINDEX DATABASE. Even REINDEX SYSTEM did not solve. Is this problem related with recovery mode of my server ? Unsure at the moment as there is not enough information to come to any conclusions. Questions: 1) Do you still have the logs from when you added the 5 new schema and do they show any warnings, errors, etc at or after that time? 2) Are you seeing any warnings, errors, etc in the logs currently? 3) Is the replication for all tables? 4) The exact same query works without a problem on the replicated server, correct? 5) In the Postgres server that is being replicated to are there any log entries that might be of concern? 6) Is it possible to get a stack trace of the crash?: https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD -- Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html -- Adrian Klaver adrian.kla...@aklaver.com
Re: JSONB Array of Strings (with GIN index) versus Split Rows (B-Tree Index)
On 2019-02-04 05:34, Syed Jafri wrote: > |-|--|-|--| > | Receiver | Event | Date| > Location| > |-|--|-|--| > | Alpha | 3| 12 | USA > | > |-|--|-|--| > | Bravo | 3| 12 | USA > | > |-|--|-|--| > | Charlie | 3| 12 | USA > | > |-|--|-|--| Please forgive a naive question, but doesn't this simply cry out for a normalization step? EventID Date Location 3 12 USA Receiver EventID Alpha 3 Bravo 3 Charlie 3 If you want to use JSON by any means necessary, perhaps a simpler key/value store is more appropriate than a relational DB like Postgres? -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet and on broken lists which rewrite From, fetch the TXT record for no-use.mooo.com.
Re: JSONB Array of Strings (with GIN index) versus Split Rows (B-Tree Index)
On Sun, Feb 3, 2019 at 10:35 PM Syed Jafri wrote: > · Receiver names are of the type (a-z, 1-5, .) > > · 95% of all queries currently look like this: SELECT * FROM table > WHERE Receiver = Alpha, with the new format this would be SELECT * FROM table > WHERE receivers @> '"Alpha"'::jsonb; > 3. Which option is more efficient? Which is faster? I'd probably develop a performance test for the model and planned queries and experiment with: 1. text arrays 2. jsonb arrays 3. partitioning David J.
Re: Server goes to Recovery Mode when run a SQL
Olá Marcos, On Mon, 2019-02-04 at 08:33 -0700, PegoraroF10 wrote: > About replication ... Logical Replication with CREATE > PUBLICATION/SUBSCRIPTION. > > Yes, some DDL commands were ran on that server but none of them were > related > with that select. > Let me explain better. We have a single server with a single database > on it. > Each customer has its own schema and connects to it to work > exclusively on > that schema. So, sometimes we add some customer or change something > on an > old one. But this DDL change we could ran is not related with that > schema we > are talking. Schemas can have different structures but that schema > which > puts my server on recovery mode was not changed. > > Maybe something related happened some days ago. When we start a new > customer > we add a schema, put all their tables on it and it´s ok. Our server > has > today 90 schemas and each schema has 100 tables, resulting in 9000 > tables. > Some days ago we added 5 new customers on same day, so we added 500 > tables. > Then, when we did that some selects on system tables were very very > slow and > that was only solved when we did a REINDEX DATABASE. Even REINDEX > SYSTEM did > not solve. Is this problem related with recovery mode of my server ? > > I trust that you saved the output from your "create" scripts. I would find those five log files and see if any errors occurred. Also, you would have to run them on the "subscriber" server first. So, if you "diff'd" the log files for "escola-53" (or whatever) from the publication and the subscriber servers, they should be similar in all respects? I don't know the answer to that question. Chapter 31.4 in the doco is interesting reading. Cheers, Robert
