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.
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?
https://karriere.rosebikes.de/jobs/40986620/-Senior-PHP-Backend-Developer-m-w-d-/
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 https://hur.st/bloomfilter/?n=1000000000&p=1.0E-7&m=&k=
Anyone know of an alternative to postico that won't make me guilty regularly for not forking over 60€?
National Park Services (NPS) ‘Park Tiles’ [public web mapping, USA]
--
https://www.nps.gov/maps/tools/park-tiles/index.html#12/38.5640/-107.6372 <-- entry point
--
[also a mobile app ]
“Park Tiles is a suite of online basemaps designed to fit the National Park Service’s graphic identity. Built with simplicity and flexibility in mind, Park Tiles basemaps can be used as stand-alone reference maps, or customized web maps with additional data overlays. Park Tiles features NPS-sourced data inside park boundaries, and relies on OpenStreetMap data to provide additional context…”
#GIS #spatial #mapping #PostGIS #PostgresSQL #QGIS #vectortiles #opendata #opensource #gischat #ParkTiles #OSM #basemaps #NPS #maps #webmaps
@NPS
Ódio desbloqueado: configurar #Django + #PostgresSQL no #Docker/#Podman.
Importing the #Google #ngram #Data set into #PostgresSQL.
I'm almost done with the bi-grams.
I've got about ~900GB more to import, then it's on to the tri-grams.
This is an entire, unfiltered set, that I'm going to backup first and put in cold storage.
Then I'm going to filter out rows that have characters that aren't allowed in #HashTags. This is the dataset that will power #FediMod's hashtag #accessibility service.
Quest:
Existence of an #ODBC binding for Mastodon that decouples it from #PostgresSQL.
#MySQL only comes into play due to our mysql2odbc library for decoupling MySQL apps.
Based on our expertise and 30+ years of experience re #DataAcces, #DataConnectivity (ODBC and #JDBC), and DBMS tech (see our #VirtuosoRDBMS), I know we can build such a binding if need be.
Initially though, I am curious about what may already exist rather than what’s possible
@tigase in the latest release of your server you mention emoji support for #MySQL , what about #PostgresSQL ?
@rysiek #Oracle free is definitely a big plus. I did a little performance testing last year #MariaDB was a little faster. But not fast enough to say "must change".
I'd go with the consensus #MariaDB for legacy stuff. #PostgresSQL for anything new.