home.social

#postgressql — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #postgressql, aggregated by home.social.

  1. Interessanter Workload - Weil wir meetings oft zur Stunde anfangen hat ai Firma die llm services rund um meetings anbietet eine hübsche Sägezahnfunktion in ihren Graphen :)

    recall.ai/blog/postgres-postma

    (Geht im Post primär um #PostgresSQL)

  2. Interessanter Workload - Weil wir meetings oft zur Stunde anfangen hat ai Firma die llm services rund um meetings anbietet eine hübsche Sägezahnfunktion in ihren Graphen :)

    recall.ai/blog/postgres-postma

    (Geht im Post primär um #PostgresSQL)

  3. Interessanter Workload - Weil wir meetings oft zur Stunde anfangen hat ai Firma die llm services rund um meetings anbietet eine hübsche Sägezahnfunktion in ihren Graphen :)

    recall.ai/blog/postgres-postma

    (Geht im Post primär um #PostgresSQL)

  4. Interessanter Workload - Weil wir meetings oft zur Stunde anfangen hat ai Firma die llm services rund um meetings anbietet eine hübsche Sägezahnfunktion in ihren Graphen :)

    recall.ai/blog/postgres-postma

    (Geht im Post primär um #PostgresSQL)

  5. Interessanter Workload - Weil wir meetings oft zur Stunde anfangen hat ai Firma die llm services rund um meetings anbietet eine hübsche Sägezahnfunktion in ihren Graphen :)

    recall.ai/blog/postgres-postma

    (Geht im Post primär um #PostgresSQL)

  6. Next why the database, why #postgressql why not #mariadb or something else?
    Well this is basically based on experience.

    When it comes to out of the box performance and stability, I find that postgres. Also when you need to adapt it for scalability in particular sharding I find this to be significantly easier than in other database.

    It is not that the other DBs are bad. I find Postgres better.

  7. Next why the database, why #postgressql why not #mariadb or something else?
    Well this is basically based on experience.

    When it comes to out of the box performance and stability, I find that postgres. Also when you need to adapt it for scalability in particular sharding I find this to be significantly easier than in other database.

    It is not that the other DBs are bad. I find Postgres better.

  8. Next why the database, why #postgressql why not #mariadb or something else?
    Well this is basically based on experience.

    When it comes to out of the box performance and stability, I find that postgres. Also when you need to adapt it for scalability in particular sharding I find this to be significantly easier than in other database.

    It is not that the other DBs are bad. I find Postgres better.

  9. Next why the database, why #postgressql why not #mariadb or something else?
    Well this is basically based on experience.

    When it comes to out of the box performance and stability, I find that postgres. Also when you need to adapt it for scalability in particular sharding I find this to be significantly easier than in other database.

    It is not that the other DBs are bad. I find Postgres better.

  10. Next why the database, why #postgressql why not #mariadb or something else?
    Well this is basically based on experience.

    When it comes to out of the box performance and stability, I find that postgres. Also when you need to adapt it for scalability in particular sharding I find this to be significantly easier than in other database.

    It is not that the other DBs are bad. I find Postgres better.

  11. Does anybody know if Postgres added more strict query argument checking since PG14?

    I'm seeing things start to fail (when trying to compare string to int so always invalid) that didn't fail on PG17 that didn't fail on earlier releases (and also working on SQLite as everything is being fronted by Sequlize)

    #database #PostgresSQL #postgres

  12. Does anybody know if Postgres added more strict query argument checking since PG14?

    I'm seeing things start to fail (when trying to compare string to int so always invalid) that didn't fail on PG17 that didn't fail on earlier releases (and also working on SQLite as everything is being fronted by Sequlize)

    #database #PostgresSQL #postgres

  13. Does anybody know if Postgres added more strict query argument checking since PG14?

    I'm seeing things start to fail (when trying to compare string to int so always invalid) that didn't fail on PG17 that didn't fail on earlier releases (and also working on SQLite as everything is being fronted by Sequlize)

    #database #PostgresSQL #postgres

  14. Does anybody know if Postgres added more strict query argument checking since PG14?

    I'm seeing things start to fail (when trying to compare string to int so always invalid) that didn't fail on PG17 that didn't fail on earlier releases (and also working on SQLite as everything is being fronted by Sequlize)

    #database #PostgresSQL #postgres

  15. Does anybody know if Postgres added more strict query argument checking since PG14?

    I'm seeing things start to fail (when trying to compare string to int so always invalid) that didn't fail on PG17 that didn't fail on earlier releases (and also working on SQLite as everything is being fronted by Sequlize)

    #database #PostgresSQL #postgres

  16. PostgreSQL permissions are driving me up the wall.

    GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA test TO user;

    This only appears to apply to existing tables and needs to be run again after any new tables created.

    Anybody know a way to have it apply at the SCHEMA level including new tables?

    #SQL #PostgresSQL

  17. PostgreSQL permissions are driving me up the wall.

    GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA test TO user;

    This only appears to apply to existing tables and needs to be run again after any new tables created.

    Anybody know a way to have it apply at the SCHEMA level including new tables?

    #SQL #PostgresSQL

  18. PostgreSQL permissions are driving me up the wall.

    GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA test TO user;

    This only appears to apply to existing tables and needs to be run again after any new tables created.

    Anybody know a way to have it apply at the SCHEMA level including new tables?

    #SQL #PostgresSQL

  19. PostgreSQL permissions are driving me up the wall.

    GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA test TO user;

    This only appears to apply to existing tables and needs to be run again after any new tables created.

    Anybody know a way to have it apply at the SCHEMA level including new tables?

    #SQL #PostgresSQL

  20. PostgreSQL permissions are driving me up the wall.

    GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA test TO user;

    This only appears to apply to existing tables and needs to be run again after any new tables created.

    Anybody know a way to have it apply at the SCHEMA level including new tables?

    #SQL #PostgresSQL

  21. Gerade auf der Arbeit die Datenbank durch Komprimierung um den Faktor 4 verkleinert und die Performance verbessert. Fühlt sich gut an.
    Danke #Timescale #PostgresSQL

  22. I want to move my #Postgres database from the VPS that Mastodon is on.

    I have a shared hosting package from NameCheap that I am paying for that is hosting static websites and not using any of the 50 allocated #PostgresSQL databases.

    Are there any downsides to moving my DB to that shared hosting setup? #MastoAdmin

    It's the Steller Plus plan at NameCheap

    EDIT: Resolved. Several people here and elsewhere report that this shouldn't be done because of degraded performance.

  23. I want to move my #Postgres database from the VPS that Mastodon is on.

    I have a shared hosting package from NameCheap that I am paying for that is hosting static websites and not using any of the 50 allocated #PostgresSQL databases.

    Are there any downsides to moving my DB to that shared hosting setup? #MastoAdmin

    It's the Steller Plus plan at NameCheap

    EDIT: Resolved. Several people here and elsewhere report that this shouldn't be done because of degraded performance.

  24. I want to move my #Postgres database from the VPS that Mastodon is on.

    I have a shared hosting package from NameCheap that I am paying for that is hosting static websites and not using any of the 50 allocated #PostgresSQL databases.

    Are there any downsides to moving my DB to that shared hosting setup? #MastoAdmin

    It's the Steller Plus plan at NameCheap

    EDIT: Resolved. Several people here and elsewhere report that this shouldn't be done because of degraded performance.

  25. I want to move my #Postgres database from the VPS that Mastodon is on.

    I have a shared hosting package from NameCheap that I am paying for that is hosting static websites and not using any of the 50 allocated #PostgresSQL databases.

    Are there any downsides to moving my DB to that shared hosting setup? #MastoAdmin

    It's the Steller Plus plan at NameCheap

    EDIT: Resolved. Several people here and elsewhere report that this shouldn't be done because of degraded performance.

  26. I want to move my #Postgres database from the VPS that Mastodon is on.

    I have a shared hosting package from NameCheap that I am paying for that is hosting static websites and not using any of the 50 allocated #PostgresSQL databases.

    Are there any downsides to moving my DB to that shared hosting setup? #MastoAdmin

    It's the Steller Plus plan at NameCheap

    EDIT: Resolved. Several people here and elsewhere report that this shouldn't be done because of degraded performance.

  27. Hab da ein #Jobangebot: #PHP, #Spryker, #PostgresSQL, #graphql in cooler Firma bei 100% #homeoffice oder wahlweise in #Essen oder #Bocholt. Dazu gibt's #Scrum (mehr oder weniger ;-) ), Praktika in anderen Bereichen des Unternehmens, und generell ein prima #Arbeitsklima.

    Gerne teilen für mehr Reichweite. Gibt's im Fediverse Hashtags, die sonst noch relevant wären?

    karriere.rosebikes.de/jobs/409

    #FediJobs #FediHire #getFedihired

  28. Hab da ein #Jobangebot: #PHP, #Spryker, #PostgresSQL, #graphql in cooler Firma bei 100% #homeoffice oder wahlweise in #Essen oder #Bocholt. Dazu gibt's #Scrum (mehr oder weniger ;-) ), Praktika in anderen Bereichen des Unternehmens, und generell ein prima #Arbeitsklima.

    Gerne teilen für mehr Reichweite. Gibt's im Fediverse Hashtags, die sonst noch relevant wären?

    karriere.rosebikes.de/jobs/409

    #FediJobs #FediHire #getFedihired

  29. Hab da ein #Jobangebot: #PHP, #Spryker, #PostgresSQL, #graphql in cooler Firma bei 100% #homeoffice oder wahlweise in #Essen oder #Bocholt. Dazu gibt's #Scrum (mehr oder weniger ;-) ), Praktika in anderen Bereichen des Unternehmens, und generell ein prima #Arbeitsklima.

    Gerne teilen für mehr Reichweite. Gibt's im Fediverse Hashtags, die sonst noch relevant wären?

    karriere.rosebikes.de/jobs/409

    #FediJobs #FediHire #getFedihired

  30. Hab da ein #Jobangebot: #PHP, #Spryker, #PostgresSQL, #graphql in cooler Firma bei 100% #homeoffice oder wahlweise in #Essen oder #Bocholt. Dazu gibt's #Scrum (mehr oder weniger ;-) ), Praktika in anderen Bereichen des Unternehmens, und generell ein prima #Arbeitsklima.

    Gerne teilen für mehr Reichweite. Gibt's im Fediverse Hashtags, die sonst noch relevant wären?

    karriere.rosebikes.de/jobs/409

    #FediJobs #FediHire #getFedihired

  31. Hab da ein #Jobangebot: #PHP, #Spryker, #PostgresSQL, #graphql in cooler Firma bei 100% #homeoffice oder wahlweise in #Essen oder #Bocholt. Dazu gibt's #Scrum (mehr oder weniger ;-) ), Praktika in anderen Bereichen des Unternehmens, und generell ein prima #Arbeitsklima.

    Gerne teilen für mehr Reichweite. Gibt's im Fediverse Hashtags, die sonst noch relevant wären?

    karriere.rosebikes.de/jobs/409

    #FediJobs #FediHire #getFedihired

  32. Guest @FranckPachot from #yugabyte joins our very own @noctarius2k in this episode of the weekly, 20 min #CloudCommute #podcast, talking about #distributedsql, #postgresql , #vectordatabases, and more. Tune in!

    The 🎙️ is available on Spotify, iTunes, Pandora, Amazon Music, and more.

    🎥👉 youtu.be/1EAKqwcP2SY

    #vectordatabase #vectorsearch #vectordb #database #databases #postgres #postgressql

  33. Guest @FranckPachot from #yugabyte joins our very own @noctarius2k in this episode of the weekly, 20 min #CloudCommute #podcast, talking about #distributedsql, #postgresql , #vectordatabases, and more. Tune in!

    The 🎙️ is available on Spotify, iTunes, Pandora, Amazon Music, and more.

    🎥👉 youtu.be/1EAKqwcP2SY

    #vectordatabase #vectorsearch #vectordb #database #databases #postgres #postgressql

  34. Guest @FranckPachot from #yugabyte joins our very own @noctarius2k in this episode of the weekly, 20 min #CloudCommute #podcast, talking about #distributedsql, #postgresql , #vectordatabases, and more. Tune in!

    The 🎙️ is available on Spotify, iTunes, Pandora, Amazon Music, and more.

    🎥👉 youtu.be/1EAKqwcP2SY

    #vectordatabase #vectorsearch #vectordb #database #databases #postgres #postgressql

  35. Guest @FranckPachot from #yugabyte joins our very own @noctarius2k in this episode of the weekly, 20 min #CloudCommute #podcast, talking about #distributedsql, #postgresql , #vectordatabases, and more. Tune in!

    The 🎙️ is available on Spotify, iTunes, Pandora, Amazon Music, and more.

    🎥👉 youtu.be/1EAKqwcP2SY

    #vectordatabase #vectorsearch #vectordb #database #databases #postgres #postgressql

  36. Guest @FranckPachot from #yugabyte joins our very own @noctarius2k in this episode of the weekly, 20 min #CloudCommute #podcast, talking about #distributedsql, #postgresql , #vectordatabases, and more. Tune in!

    The 🎙️ is available on Spotify, iTunes, Pandora, Amazon Music, and more.

    🎥👉 youtu.be/1EAKqwcP2SY

    #vectordatabase #vectorsearch #vectordb #database #databases #postgres #postgressql

  37. Есть причина, по которой лучше выбрать #mariadb нежели #postgressql?

  38. Есть причина, по которой лучше выбрать #mariadb нежели #postgressql?

  39. Есть причина, по которой лучше выбрать #mariadb нежели #postgressql?

  40. Есть причина, по которой лучше выбрать #mariadb нежели #postgressql?

  41. Есть причина, по которой лучше выбрать #mariadb нежели #postgressql?

  42. It turns out that a #PostgresSQL table to store URLs crawled is a bad idea: the table is currently 749G on disk. In contrast, a bloom filter with a 1e-7 error for a billion items will take up about 4G hur.st/bloomfilter/?n=10000000

    #mwmbl #opensource #searchengine

  43. It turns out that a #PostgresSQL table to store URLs crawled is a bad idea: the table is currently 749G on disk. In contrast, a bloom filter with a 1e-7 error for a billion items will take up about 4G hur.st/bloomfilter/?n=10000000

    #mwmbl #opensource #searchengine