Live data from Hacker News

Viewing profile — tomiko_nakamura

tomiko_nakamura

HN member
Joined
Thu, Jul 17, 2014, 4:16 PM UTC
HN karma
45
Public activity
31 items

About tomiko_nakamura

No profile information was provided.

Recent public activity

  1. comment
    Comment #9131856

    MVCC means "Multiversion Concurrency Control" and yes, that's pretty much exactly how it works (creating copies of the rows, so that different snapshots see different rows). In pra…

  2. comment
    Comment #9131838

    I don't think XML was all that widely used, and the implementation looked more "looks interesting, let's develop something and people will use that". With JSONB it's more like "peo…

  3. comment
    Comment #9131815

    I think that if you're using JSONB for data that can be easily stored in a proper tabular form (aka relation), you're doing it wrong. No doubt there will be people using it this wa…

  4. comment
    Comment #9131787

    People are working on other storage types for PostgreSQL. That's all I can say at this moment.

  5. comment
    Comment #9131777

    Yeah, IRC is a good place to ask too. The obvious problem is that not all developers hang there all the time, so for longer discussions the mailing lists are better (and you can ju…

  6. comment
    Comment #9130006

    PostgreSQL does not have in-place update in the first place, on every UPDATE it does a DELETE+INSERT. So "partial update" does not make much sense, because you'll create a new copy…

  7. comment
    Comment #9129992

    I really wonder what you mean by UPSERTS. Because the traditional meaning for UPSERT is "UPDATE if exists, INSERT otherwise", aka MERGE. And you're right PostgreSQL is missing that…

  8. comment
    Comment #9129977

    It doesn't have MySQL-like pluggable storage, and frankly I'm thankful for that. How many of the MySQL storage engines actually work, including transactions for queries working wit…

  9. comment
    Comment #9129936

    I'm not saying "plan locking" is not a useful feature in some cases, and maybe it would really solve this particular issue. But my experience is that when people say "I need it" in…

  10. comment
    Comment #9129164

    Expression indexes are nice, and you can still do that. It however requires you to know what you'll be looking for (and create index on that particular expression). The stuff I fin…

  11. comment
    Comment #9129150

    Why? What mistake? I mean, many people won't use that, but for many it's very handy. And the features delivered with JSONB (e.g. the indexing) is way better than what was available…

  12. comment
    Comment #9129142

    JSONB had issue with compression, because the compression is decided on the fly by checking if first part of the serialized data, and in the original format the first part was inco…

  13. comment
    Comment #9129039

    BTW I wonder what you mean by "accumulated stats" ... Regarding your senior engineers - maybe they're competent, maybe not. But most importantly, the experience from one database i…

  14. comment
    Comment #9129029

    The only response I have to that is "talk to developers on the mailing list" (either pgsql-performance or pgsql-hackers). Maybe it's possible to improve the planning - maybe your q…

  15. comment
    Comment #8943138

    IANAL, of course, but ... 1. There's no suitable legal entity that could receive the copyright/rights on behalf of the PostgreSQL project. There are entities handling domains/... b…

  16. comment
    Comment #8876114

    I don't really see how that matters. This only shows how utterly broken the concept of "patch Tuesdays" is ... If you plan your internal deployment updates based on the belief that…

  17. comment
    Comment #8875959

    Well, they thought so too. And it turned not to be true. And now they're blaming the others.

  18. comment
    Comment #8875430

    If this is used just as an AP, how much harm can a baseband backdoor do? I mean, there are no interesting sensors, the other side already knows the (approximate) location ... assum…

  19. comment
    Comment #8874033

    If you start making exceptions, everyone will want one.

  20. comment
    Comment #8874030

    You're just citing the press release (or a blog post, or whatever). How does that respond to the original question? The issue mentioned in the article [ https://code.google.com/p/g…

  21. comment
    Comment #8874011

    If you define a limit for disclosure, and then not stick to it, why to define a limit in the first place? 90 days is more than enough - if MS has a lot of internal overhead, you sh…

  22. comment
    Comment #8873986

    So, who forces Microsoft to stick to (so called) patch Tuesdays? No one, actually - it's Microsoft internal schedule, and clearly there are cases when it's absolutely unreasonable …

  23. comment
    Comment #8784362

    That really depends on what version you're using now, and what exactly you mean by scalability. If you're using 9.1 or older, you may see a significant improvement in OLTP workload…

  24. comment
    Comment #8784317

    I'm not a big fan of MongoDB, but I don't think the introduction of JSONB in PostgreSQL 9.4 makes it a dud (which does not mean MongoDB is not a dud for other reasons). JSONB allow…

  25. comment
    Comment #8784261

    We certainly are. We're operating an analytical service operated on PostgreSQL - tens of TBs of data, hundreds of machines, tens of thousands of clients. Initially it was running o…