@EvanCarroll We do fun things like write foreign data wrappers for things like Kafka, and I am currently writing a distributed transaction coordinator that plugs into the back end for managing data copied between pg versions.
@dezso In Berlin.
So a lot of things require both a knowledge of C and an understanding of Pg internals and in particular memory management.
@ChrisTravers I knew it would turn out to be something as mundane and boring as that. The real-world iStore as a Postgres datatype would seem much more fun :) Oh well, can't have it all
@ChrisTravers The former is more likely, of course, but even in that case I guess nothing prevents you from amusing yourself by imagining the latter :)
@dezso by the way, programming in C is actually fairly simple: 1. you think about your data structures. 2. You think about your memory allocation. 3. you test/debug your code. The steps I have skipped over are largely insignificant in terms of time and effort.
Yeah. I wrote a two phase commit module for one of our Pg extensions in C in basically a day (200 lines of C code). It took me about 2 hours to debug and fix it the next day and most of that was makefile framework stuff.
Next I am writing a background worker to handle what happens if the remote connections cannot be cleanly resolved during transaction commit. I will probably do that this week. But not rushing it.
I don't get to code today, which may be a good thing for this project.
i need a good and interesting data set. i need a large one that would be "batchy" and i need another that would be more transactional. the stackexchange set is not quite what i'm looking for
i have no idea what's going on. i saw some chatter about inserts but is that the problem we're trying to solve?
> When you import the data into CCI, the data is loaded either into delta rowgroup or compressed rowgroup based on the rule “If batchsize < 102400, the rows are loaded into delta rowgroup otherwise they are directly loaded into compressed rowgroup”. Minimal logging is only supported when data is directly loaded into compressed rowgroup. This means, to get minimal logging with CCI, you must use a batchsize >= 102400.