ioltas

6 ms·

1.
by ioltas 2y ago
There has been a patch to extend the COPY code with pluggable APIs, adding callbacks at start, end, and for each row processed: https://commitfest.postgresql.org/49/4681/ . I'd guess that this may fit your pur
2.
by ioltas 2y ago
The bar to merge a patch that would break on-disk format is so high that it’s really impossible to reach it ;) More seriously, we care a lot about the format of the 8k pages to ease upgrade paths as much as possible.
3.
by ioltas 2y ago
I’ve met Simon for the first time in Tokyo in 2009 for a birthday related to JPUG (Japan PostgreSQL User Group) when hot standby was getting integrated into the upstream project. I saw him last time in Prague three months ago, and we have j
4.
by ioltas 3y ago
I’ll try to do something about that tomorrow, saw your ticket.
5.
by ioltas 3y ago
There are hooks for the planner and the executor, so you could force their hand quite easily with a plan extracted from a previous EXPLAIN. Being able to pass a plan at protocol level would be more efficient, for sure. I’ve worked on Postgr
6.
by ioltas 3y ago
Thanks, glad to hear some good feedback.
7.
by ioltas 3y ago
There are many Postgres internals that people are usually not aware of, with more than one way to develop your module. I have a repo that’s a set of plugin templates here, that should be handy for your studies: https://github.com
8.
by ioltas 3y ago
I’ve been doing maintenance and bug fixes for this module for over 18 months now (last commit on HEAD seems to be mine), managing the last two releases. If you have questions and/or feedback, feel free.
9.
by ioltas 3y ago
Note that this one mentions 借地料, meaning that you are not an owner of the land, but the government is lending it to you for a yearly fee of 220,000 yens.
10.
Postgres 16 highlight – JSON predicates(paquier.xyz)
4 points by ioltas 3y ago|0 comments
11.
by ioltas 4y ago
It's been argued a few times that we should have the possibility to make an index invalid on sight with a proper ALTER INDEX command, yes.
12.
by ioltas 4y ago
FWIW, amcheck can be useful but I am not 100% sure that it can detect all the broken cases either.
13.
by ioltas 5y ago
Looking at their code tree, this is based on 11.2 ( https://www.postgresql.org/docs/11/release-11-2.html ): https://github.com/alibaba/PolarDB-for-PostgreSQL/blob/maste... So this is
14.
by ioltas 6y ago
mutt + mbsync with a local copy is also a nice combination.
15.
by ioltas 6y ago
Discussions within the core team are done on a private mailing list, so we'll know the status of things with a public announcement. Committers and contributors have no view of what gets discussed there, except if you are of course dire
16.
by ioltas 7y ago
When it comes to backup, the time it takes for the backup to complete is not a property that matters the most in my opinion. The time it takes to restore the backup matters, and being sure that the backup is able to restore and is not corru
17.
by ioltas 7y ago
Here are some slides from a presentation of Andres Freud on the matter: https://anarazel.de/talks/2018-10-25-pgconfeu-pluggable-stor... Slides 4 and 5 give some insight about the architecture changes which have been do
18.
by ioltas 7y ago
An advantage of REINDEX CONCURRENTLY is that it becomes much easier to handle dependencies of a rebuilt index with constraints, as what the feature roughly does it to add a swapping phase between the creation and the drop portions which swi
19.
by ioltas 7y ago
I am not sure, but doesn't it make also sense financially for some parents to send their kids to soroban classes because that's actually cheaper and more frequent in a week than other alternatives when they cannot go anymore to th
20.
by ioltas 7y ago
If that was not clear, the root comment mentioned that Dimitri was a committer, and it got edited afterwards. Regarding the book, I have a copy of the first edition close by (with a dedication from the author), and for application developer
21.
by ioltas 7y ago
Dimitri is a major contributor of Postgres for a very long time, still he is no committer: https://wiki.postgresql.org/wiki/Committers Saying that, the man is really cool and his book is very good, so that's a mu
22.
SQL/JSON Path and Postgres 12(paquier.xyz)
4 points by ioltas 7y ago|0 comments
23.
by ioltas 7y ago
> This is true. In fact, by far the fastest route to permanent residence in Japan is marriage. You can get PR in 3 years if you are married to a Japanese national vs 10 years if you aren't. More details on that. Getting a wedding vi
24.
by ioltas 7y ago
Postgres 12, whose development has reached feature freeze and is in a stability period, has added some support for JSON path as of SQL:2016: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit... The release
25.
Postgres adds Support for Reindex Concurrently (parallel read/writes allowed)(git.postgresql.org)
2 points by ioltas 7y ago|0 comments
26.
by ioltas 8y ago
There is a range of interesting problems here for Postgres. One is related to the costly way snapshots are built which needs to scan all entries in PGPROC to get back a list of transaction IDs. So even idle connections come at a cost. There
27.
by ioltas 8y ago
The most productive language of Gilles, well-known in the Postgres community by the way, is perl, and he can do completely crazy things with it. See for example pgbadger ( https://github.com/darold/pgbadger ), one of his
28.
PostgreSQL 11 Highlight – More Partition Pruning(paquier.xyz)
3 points by ioltas 8y ago|0 comments
29.
MERGE SQL Command Following SQL:2016 Added to Postgres(git.postgresql.org)
1 points by ioltas 8y ago|0 comments
30.
Addition of expression compilation support with LLVM JIT in PostgreSQL 11(git.postgresql.org)
1 points by ioltas 8y ago|0 comments

More ›