petergeoghegan

12 ms·

61.
by petergeoghegan 5y ago
> This is what is called "the founder's will". Just to be clear: you're saying that "the founder's will" should not be interpreted as meaning "what Alvaro Carlos Hernandez Tortosa [the founder fo
62.
by petergeoghegan 5y ago
> Fundación PostgreSQL is a 100% independent non-profit organization not tied to any company or any other institution. What about private individuals? Specifically, you? Quoting the charter here: https://postgresql.fund/d
63.
Index bloat reduced in PostgreSQL v14(cybertec-postgresql.com)
179 points by petergeoghegan 5y ago|89 comments
64.
by petergeoghegan 5y ago
> This "upstream first" approach to product kernel development and testing is extremely efficient. Google has been successfully doing this with Chrome OS and Android for a while now, and is hardly alone in the industry. This se
65.
by petergeoghegan 5y ago
It is practically essential for any RDBMS to provide non-standard statements and features. For example, even CREATE INDEX isn't in the SQL standard, since the SQL standard deliberately avoids talking about what it considers to be imple
66.
by petergeoghegan 5y ago
It's not possible to give you a simple answer, especially not without a lot more information. Perhaps you can test your workload with postgres 14 beta 1, and report any issues that you encounter to one of the community mailing lists.
67.
by petergeoghegan 5y ago
> Very interesting thanks for the update - how great is the Internet to hear directly from the developer! I see the names of a few people that also work on Postgres on this thread. We're not all that hard to get a hold of if you&#
68.
by petergeoghegan 5y ago
Thanks. I forgot to mention that the test case had constant long-running transactions, each lasting 5 minutes. Over a 4 hour period for each tested configuration. This level of improvement was possible by adding a relatively simple mechanis
69.
by petergeoghegan 5y ago
Co-author of that feature here. Clearly it doesn't eliminate the possibility of wraparound failure entirely. Say for example you had a leaked replication slot that blocks cleanup by VACUUM for days or months. It'll also block free
70.
by petergeoghegan 5y ago
Although the article doesn't mention it, index bloat will be far better controlled in Postgres 14: https://www.postgresql.org/docs/devel/btree-implementation.h... One benchmark involving a mix of queue-like i
71.
by petergeoghegan 5y ago
I would say that that's pretty dubious claim with modern versions of Postgres and MySQL/InnoDB, running on modern hardware. See for example this recent comparative Benchmark from Mark Callaghan, a well known member of the MySQL co
72.
by petergeoghegan 6y ago
The Postgres community mailing list for development work -- pgsql-hackers.
73.
by petergeoghegan 6y ago
There is also index deduplication in Postgres 13 and the B-Tree enhancements in Postgres 12. All of these enhancements significantly improved the situation for workloads affected by what the blog post calls write amplification. (I myself c
74.
by petergeoghegan 6y ago
Thanks
75.
by petergeoghegan 6y ago
I committed a patch that added a mechanism I called "bottom-up index deletion" recently: https://www.postgresql.org/docs/devel/btree-implementation.h... https://git.postgresql.org/gitweb&
76.
by petergeoghegan 6y ago
I am the author of a tool that generates wxHexEditor tags and annotations for Postgres relation files -- pg_hexedit: https://github.com/petergeoghegan/pg_hexedit I've invested quite a lot of effort in it, and it w
77.
by petergeoghegan 6y ago
> I'm calling for an strategic discussion There is practically no information about Babelfish available to analyze. You can currently request a preview of Babelfish if you have an AWS account, though I'm not aware of anyone hav
78.
by petergeoghegan 6y ago
> To announce such a big contribution to Postgres, and be it open sourced when published, is very welcome But the source code hasn't been published. As I said to you today on pgsq-hackers, that's why it hasn't been taken
79.
by petergeoghegan 6y ago
NULL values are not special as far as deduplication is concerned. They use approximately as much disk space as a non-NULL integer column without deduplication, and compress just as well with deduplication. Deduplication is effective because
80.
by petergeoghegan 6y ago
Are you aware of any contemporary on-disk or in memory DB system that typically uses a page size of 4KiB or less? And if not, are you expecting that to become a trend in the future?
81.
by petergeoghegan 6y ago
I didn't say that these specific claims are simply false. Just that they sure seem to hint at extraordinary improvements in a broad range of cases. The website itself also seems to me to be suggestive in just the same way, only much mo
82.
by petergeoghegan 6y ago
The paper says 83x, and even makes stronger claims that are fairly unqualified: In short, the experimental achievements of the PGM-index are: (i) better space occupancy than the FITing-tree by up to 75% and than the CSS-tree by a factor 83×
83.
by petergeoghegan 6y ago
Not likely. I have done a lot of work on B-Tree indexing in Postgres in the past several years, and this is all Greek to me.
84.
by petergeoghegan 6y ago
I think that you're on to something here. I write C full time, and have done so for many years. It didn't occur to me that the pointer to a pointer aspect was the source of any of the confusion until just now. Actually, I don&#x27
85.
by petergeoghegan 6y ago
It seems to me that what is at issue here is the difference between easy to understand and simple. They're not always the same thing. Simpler code tends to be easier to audit for bugs (as a practical matter).
86.
by petergeoghegan 6y ago
pg_stat_activity isn't an extension -- it's a standard system view
87.
by petergeoghegan 6y ago
I am cautiously optimistic that my own recent work on version churn in B-Tree indexes will go a long way towards fixing those problems: https://postgr.es/m/CAH2-Wz=CEKFa74EScx_hFVshCOn6AA5T-ajFAST... This can be used w
88.
by petergeoghegan 6y ago
Amazon themselves use Aurora PostgreSQL for Amazon retail fulfillment databases: https://aws.amazon.com/solutions/case-studies/amazon-fulfill...
89.
by petergeoghegan 6y ago
Your point about MyRocks is a good one. It's also true that MyRocks takes a similar approach to Postgres when it comes to implementing the higher isolation levels. It wouldn't make sense to add InnoDB style next-key locks to MyRoc
90.
by petergeoghegan 6y ago
Recovery in Postgres is simplified and sped up considerably by the approach taken to MVCC. Same is true with transaction rollback. SQL Server users (on recent SQL Server versions) can optionally get a similar trade-off by enabling constant

More ›