On 10. 02. 21 09:14, Rajnish Vishwakarma wrote:
Hi Postgres Team,
The below are the scenarios which we are dealing with.
1) There are 20 Tables - On an average each having 150 columns.
2) There are 20 Threads Handled by Thread Pool Executor ( here we are
using Python's - psycopg2 module / l
evroom organisers, one of the best rooms,
was a blast.
Best regards, Cen
On 16/02/2023 17:07, David G. Johnston wrote:
No, the planner may not cause execution. While I could imagine
extending EXPLAIN to somehow retrieve and maybe even try alternative
plans that have been fully constructed today I'm not holding my breath.
There is little reason for the project to
On 16/02/2023 17:15, Ron wrote:
On 2/16/23 09:47, cen wrote:
Hi,
I am running the same application (identical codebase) as two
separate instances to index (save) different sets of data. Both run
PostgreSQL 13.
The queries are the same but the content in actual databases is
different
Likely to be safe, you'd just include both. The problem is that the
query planner makes use of equivalence classes to deduce equivalence
in quals.
If you have a query such as:
select * from t1 inner join t2 on t1.x = t2.y where t1.x = 3;
then the planner can deduce that t2.y must also be 3 and
re up, pgpool
reports down and similar scenarios and then you need to run the precise
sequence of pcp commands to recover
or destroy your whole cluster in the process if you mistype.
I haven't used patroni yet but it surely can't be worse.
Best regards, cen
If MSFT is the sole holder of the copyright, then they can relicense
it as they see fit. *I think* that they can only change the license on
*newer* versions, so you'd be able to keep using the latest OSS version.
That is correct. If I get a version 1 of your program under license A
you can't
From my experience, and some might disagree, I prefer to do db stores
purely in UTC and handle timezones in ORM or client side.
The only time I actually needed to store timezone information in a
dedicated column is when needing to convey that information to the end
user, for example "your plan
On 21. 09. 21 23:34, Michael Lewis wrote:
Related to this current discussion and exchange of ideas... is there a
best practice for retrieving data in such a way as the rows are
localized to a timezone for where/group by purposes. That is, if I
have a table which has events, but those events be
