samokhvalov

10 ms·

91.
by samokhvalov 5y ago
Women's record is mentioned a bit earlier: > Bourke reached a depth of 73 metres – a world record – ... All the facts are correct and provided. But I agree, how they present facts looked weird to me too.
92.
by samokhvalov 5y ago
Women's CNF record currently is 73m (AIDA version, see https://www.aidainternational.org/WorldRecords/History/Const... , switch to Women). She is not WR holder, but current record is 73m and going deeper 70m w
93.
by samokhvalov 5y ago
Exactly! Great thought, it aligns with our vision. (Postgres.ai founder here)
94.
Thin PostgreSQL Clones(github.com)
114 points by samokhvalov 5y ago|36 comments
95.
by samokhvalov 5y ago
...and it is removed (well, edited) Thank you for the snapshot link.
96.
Progress bar for Postgres queries – let's dive deeper(postgres.ai)
2 points by samokhvalov 5y ago|0 comments
97.
by samokhvalov 5y ago
But in general case, such clones are not suitable for query optimization tasks. And as I already mentioned in my other comments here, thin cloning is a great way to solve the speed (and money) problem for larger DBs.
98.
by samokhvalov 5y ago
This is great that you can do that. An experimental environment must be of the same size. Ideally, absolutely the same physically, to keep the same physical layout as on prod – bloat, etc – though, sometimes it's not allowed. Another p
99.
by samokhvalov 5y ago
> If the database is too big, just use last N amount of rows from the database instead of a full dump. For SQL optimization purposes, you cannot do that – there are high chances you'll get different query plans.
100.
by samokhvalov 5y ago
Thin clones can help: https://github.com/postgres-ai/database-lab-engine
101.
PGSpider cluster engine for PostgreSQL developed by Toshiba(github.com)
2 points by samokhvalov 5y ago|0 comments
102.
Database Lab Engine 3.0 for PostgreSQL(github.com)
1 points by samokhvalov 5y ago|0 comments
103.
Postgres.ai open-sourced Database Lab UI in DLE 3.0, a Postgres cloning tool(postgres.ai)
4 points by samokhvalov 5y ago|0 comments
104.
Partial, covering, and multicolumn indexes may slow down UPDATEs in Postgres(postgres.ai)
2 points by samokhvalov 5y ago|0 comments
105.
How partial, covering, and multicolumn indexes may slow down UPDATEs in Postgres(postgres.ai)
2 points by samokhvalov 5y ago|0 comments
106.
Babelfish, SQL Server compatibility for Postgres created by AWS, is open-sourced(github.com)
2 points by samokhvalov 5y ago|0 comments
107.
Useful queries to analyze PostgreSQL lock queues(postgres.ai)
3 points by samokhvalov 5y ago|0 comments
108.
StackGres 1.0 – Postgres on K8s with 120+ extensions(gitlab.com)
4 points by samokhvalov 5y ago|0 comments
109.
Zero-Downtime Postgres Schema Migrations Need lock_timeout and Retries(postgres.ai)
2 points by samokhvalov 5y ago|0 comments
110.
Zero-downtime Postgres schema migrations need this: lock_timeout and retries(postgres.ai)
8 points by samokhvalov 5y ago|0 comments
111.
by samokhvalov 5y ago
Take a look at Database Lab: https://postgres.ai/products/database-migration-testing The idea is to use block-level copy-on-write (ZFS by default, LVM2 is an option too, though less powerful) to be able to get thin clo
112.
What is a slow PostgreSQL query?(postgres.ai)
3 points by samokhvalov 5y ago|0 comments
113.
by samokhvalov 5y ago
They have an interesting section, "Beware: don't (over) use nested transactions", in their blog post: https://www.cockroachlabs.com/blog/nested-transactions-in-co... > ...we do not recommend their use
114.
by samokhvalov 5y ago
What does "appropriately" mean in this context?
115.
PostgreSQL Subtransactions Considered Harmful(postgres.ai)
110 points by samokhvalov 5y ago|41 comments
116.
Database Lab Engine – instant Postgres clones for development and testing(gitlab.com)
2 points by samokhvalov 5y ago|0 comments
117.
WAL-G 1.0: unified backup tool for PostgreSQL, MySQL, SQL Server, MongoDB, Redis(github.com)
4 points by samokhvalov 5y ago|2 comments
118.
by samokhvalov 5y ago
Great extension, yes. There is overhead when enabling the timing and buffers options, but sometimes it's not big [1] But auto_explain solves only part of the task – you can see what happened, but cannot see the answers to "what if
119.
by samokhvalov 5y ago
> tools to screw up table statistics Perhaps you already know these, but just in case: - https://github.com/ossc-db : pg_dbms_stats, pg_store_plans, pg_hint_plan - https://github.com/HypoPG/hypopg
120.
by samokhvalov 5y ago
> Different table statistics can cause the planner to go in wildly different directions Exactly. That's why my team and I (Postgres.ai) have developed Database Lab Engine [1] and a chatops tool for SQL optimization, Joe bot [2], bot

More ›