Live data from Hacker News

Viewing profile — pgguru

pgguru

HN member
Joined
Fri, May 05, 2023, 6:29 PM UTC
HN karma
16
Public activity
13 items

About pgguru

Postgres guy. Crunchy, Snowflake. david@pgguru.net

Recent public activity

  1. comment
    Comment #45816194

    I think we have recently merged (or are getting ready to merge) REST catalog support, so that will open some things up in this department.

  2. comment
    Comment #45815519

    For testing, we at least have a Dockerfile to automate the setup of the pgduck_server and a minio instance so it Just Works™ with the extensions installed in your local Postgres cl…

  3. comment
    Comment #45814546

    Hypertables definitely had the arrays columns auto-expanding with the custom node type. Not sure what else it would look like for what you describe. That said, don't sleep on the "…

  4. comment
    Comment #45814385

    Boils down to design decisions; see: https://news.ycombinator.com/item?id=45813631

  5. comment
    Comment #45814375

    Well, dealing with large analytics queries will always perform better with larger amounts of memory... :D You can perhaps tune things to perform based on the amount of system memor…

  6. comment
    Comment #45814124

    We have some level of external iceberg table read-only support, but it is limited at the moment. See this example/caveat: https://github.com/Snowflake-Labs/pg_lake/blob/main/docs/f…

  7. comment
    Comment #45814046

    DuckDB provided a lot of infrastructure for reading/writing parquet files and other common formats here. It also was inherently multi-threaded and supported being embedded in a lar…

  8. comment
    Comment #45813992

    In any query engine you can execute the same query in different ways. The more restrictions that you can apply on the DuckDB side the less data you need to return to Postgres. For …

  9. comment
    Comment #45813791

    Hi, what types are you expecting to see that aren't supported? I believe we had support for most/all builtin postgres types.

  10. comment
    Comment #45813556

    DuckDB secrets management supports custom IAM roles and the like; at this point we are basically treating the pgduck_server external system as a black box. For the postgres grants …

  11. comment
    Comment #45813337

    You create foreign tables in postgres using either the pg_lake_table wrapper or pg_lake_iceberg. Once those tables exist, queries against them are able to either push down entirely…

  12. comment
    Comment #45813268

    What has been pointed out from the README; also: - Separation of concerns, since with a single external process we can share object store caches without complicated locking dances …

  13. comment
    Comment #45813217

    Hi, one of the developers here. You define credentials that can access the S3 buckets and use those as DuckDB secrets, usually in an init script for pgduck_server. (You can see som…