samokhvalov

9 ms·

61.
by samokhvalov 4y ago
This is too reactive approach, isn't it? Imagine a system that could do this in CI/CD pipelines: 1) first, run all the tests on a tiny DB as usual 2) extract queries 3) run them against full-size DB branch/thin clone (thin pr
62.
by samokhvalov 4y ago
not sure about petabytes (yet), but for dozens of TiB, we are fine – DB branching, thin clones, CoW are to the rescue.
63.
by samokhvalov 4y ago
Agreed on compliance part – of course, in many cases (not in all though) PII must not be in dev/test envs. Although, cannot agree with the former part. If your tests are running 2 days on a full size clone, and it's an OLTP case,
64.
by samokhvalov 4y ago
> Use a helm chart and just bring your own little database for dev test and e2e tests. dev, test, and e2e tests should be done against full-size db clones
65.
Continuous Profiling with Coroot and Pyroscope(github.com)
2 points by samokhvalov 4y ago|0 comments
66.
by samokhvalov 4y ago
I see to use cases: - disable for all - disable only for my session, to check what would happen with the plan, and only then decide to proceed with disabling for all (or to drop it) ALTER is quite invasive way, even more than "UPDATE .
67.
by samokhvalov 4y ago
There is an opinion that it's unsafe: https://twitter.com/petervgeoghegan/status/15991919640456724... There was an extension from Teodor some time ago, plantuner, to disable indexes in a session or globally (
68.
BPF-based lock tracer for the Postgres(github.com)
1 points by samokhvalov 4y ago|0 comments
69.
by samokhvalov 4y ago
Thanks!! (postgres.fm co-host)
70.
Postgres: Safely renaming a table with no downtime using updatable views(brandur.org)
4 points by samokhvalov 4y ago|0 comments
71.
by samokhvalov 4y ago
These tools remove bloat. Autovacuum removes dead tuples. They are often confused, but dead tuple and bloat are different though connected concepts. A lot of accumulated dead tuples (row versions marked dead but still present occupying spac
72.
by samokhvalov 4y ago
Not often. And depending of what is considered as base – only the core Postgres code, or contrib modules (shipped with it and supported by community). Extension/contrib -> core is a very rare event. For example, it happened with XML
73.
by samokhvalov 4y ago
Good point. I wonder if pg_squeeze would work well in a large-scale heavy-writes case. There is a very sad and hard limit of single-threaded walsender that can saturate a single core (depends on CPU and schema / writes complexity; for
74.
by samokhvalov 4y ago
I didn't discuss money and profit, neither I discussed pgpro employees. There is difference between people and organizations, though any organization is created by people. The question I raised was about the global Postgres community a
75.
by samokhvalov 4y ago
It would be great to see monitoring of this thing under load – I mean the Postgres part of it, how it's loaded, how many connections used, query analysis, etc.
76.
by samokhvalov 4y ago
Comparing tree structures can be used to have diff of EXPLAIN plans. During query optimization, it might make a lot of sense.
77.
Using BUFFERS for Postgres query optimization(pgmustard.com)
3 points by samokhvalov 4y ago|0 comments
78.
Animated Postgres Execution Plan(twitter.com)
3 points by samokhvalov 4y ago|0 comments
79.
by samokhvalov 4y ago
I don't think I understand you. 1 word is 8 bytes, and if you use two columns, the first one having size 2 bytes, and the second – 8 bytes, you'll end up spending 8 + 8 = 16 bytes, because the first one (2byte in length) will be a
80.
Postgres Schema Change Mistakes(postgres.ai)
4 points by samokhvalov 4y ago|0 comments
81.
Common Postgres schema change mistakes(postgres.ai)
5 points by samokhvalov 4y ago|0 comments
82.
by samokhvalov 4y ago
The problem with Aurora's thin clones is extra cost each clone adds For CI/CD, you want multiple clones running on the same compute power, in a shared environment, to keep the budget constant
83.
by samokhvalov 4y ago
Agreed, this direction is underestimated and should be developed better -- we (Postgres.ai) do it for any Postgres with our Database Lab Engine [1], and Neon would bring even more power if it's installed on production [1] https:/
84.
A cross-account database vulnerability in Azure PostgreSQL(wiz.io)
60 points by samokhvalov 4y ago|15 comments
85.
YDB – distributed DBMS that combines HA, scalability, strict consistency, ACID(github.com)
5 points by samokhvalov 4y ago|0 comments
86.
Database Lab Engine 3.1 for PostgreSQL(github.com)
2 points by samokhvalov 5y ago|0 comments
87.
by samokhvalov 5y ago
Thanks for mentioning. Alexander also presented OrioleDB in English at an EDB's event: https://vimeo.com/649616139
88.
by samokhvalov 5y ago
If not Kubernetes, check out this: https://github.com/vitabaks/postgresql_cluster – it's Postgres + patroni + pgBouncer + WAL-G or pgBackRest + Netdata + more, managed by Ansible. If you do want to use Kubernetes,
89.
OrioleDB – solving some PostgreSQL wicked problems(github.com)
308 points by samokhvalov 5y ago|95 comments
90.
by samokhvalov 5y ago
11 minutes is STA – static breath-holding. Of course, without movements, you can hold breath much longer. Here are current AIDA STA WR numbers: https://www.aidainternational.org/WorldRecords/History/Stati... – leg

More ›