5 ms·

- the idea behind storing the raw feed items instead of processed ones is - what happens if your processing logic changes 6 months down the line? - for exampl

- the idea behind storing the raw feed items instead of processed ones is - what happens if your processing logic changes 6 months down the line? - for example today you decide you want to remove all extra spaces and lowercase all titles before storing them - 6 months down the line you want to revert, what now?

setr 3mo ago
For that purpose, you’re perfectly well off just leaving it as an opaque blob; compress, base64 encode and stuff it into a string/varbinary column and call it a day. You don’t even need to store it in pg itself; stuff it into a cheaper datastore like s3 and just have the locations stored in pg. The only thing to optimize for is cost & storage. Access/retrieval doesn’t matter for a once in 6 months process. Also what is this revolting formatting strategy you’ve found?
munch117 3mo ago
Absolutely store the raw data. For the reasons you state. But also store derived data. Titles, authors, dates, article texts. You need those for whatever your application does. You don't want your application logic to be working with the raw text. > how will you handle updates to the feed? When polling, consider using HTTP HEAD to check for changes before GET. What you do when an article ID reappears with different content, that up to you. I think readers usually replace the old entry with the new content, silently. But it's not the only option.
- vivzkestrel 3mo ago
  so how do you store raw xml data in postgres?
  - paulryanrogers 3mo ago
    As text or XML column type. IME a document store or columnar backend is significantly cheaper if you're not querying it from SQL.
    - vivzkestrel 3mo ago
      - there is definitely one dilemma here - if you split the rss document into its "items" i am not sure if you can store each item separately inside postgres using that XML data type - if you store the whole document, you end up with a problem when say the feed partially updates after a few minutes - one suggestion i hear from r/PostgreSQL is that you store the XML blob somewhere else like hstore or something and somehow index it back to postgres. I wonder how that works conceptually / architecturally speaking
      - paulryanrogers 3mo ago
        Pg can do array columns, though I don't think it's a good fit for common use cases
      - zaptheimpaler 3mo ago
        The data is probably small enough and infrequently updated such that almost anything will work. If you split the items then you would have a separate episodes table with one row per episode joined to the podcasts table. If you store the whole XML in a row then you can overwrite the row when the feed changes. Doing the parsing and splitting into episodes in DB sounds better to me because your clients will otherwise constantly be repeating that work.
  - SahAssar 3mo ago
    There is a datatype, if the XML is correct: https://www.postgresql.org/docs/current/datatype-xml.html https://www.postgresql.org/docs/current/datatype-xml.html
inigyou 3mo ago
A reader does things in realtime. You don't care what happened 6 months ago. If you did something 6 months ago you don't want to gaslight the user by pretending you did something different 6 months ago.

setr 3mo ago

For that purpose, you’re perfectly well off just leaving it as an opaque blob; compress, base64 encode and stuff it into a string/varbinary column and call it a day. You don’t even need to store it in pg itself; stuff it into a cheaper datastore like s3 and just have the locations stored in pg. The only thing to optimize for is cost & storage. Access/retrieval doesn’t matter for a once in 6 months process. Also what is this revolting formatting strategy you’ve found?

munch117 3mo ago

Absolutely store the raw data. For the reasons you state. But also store derived data. Titles, authors, dates, article texts. You need those for whatever your application does. You don't want your application logic to be working with the raw text. > how will you handle updates to the feed? When polling, consider using HTTP HEAD to check for changes before GET. What you do when an article ID reappears with different content, that up to you. I think readers usually replace the old entry with the new content, silently. But it's not the only option.

vivzkestrel 3mo ago
so how do you store raw xml data in postgres?
- paulryanrogers 3mo ago
  As text or XML column type. IME a document store or columnar backend is significantly cheaper if you're not querying it from SQL.
  - vivzkestrel 3mo ago
    - there is definitely one dilemma here - if you split the rss document into its "items" i am not sure if you can store each item separately inside postgres using that XML data type - if you store the whole document, you end up with a problem when say the feed partially updates after a few minutes - one suggestion i hear from r/PostgreSQL is that you store the XML blob somewhere else like hstore or something and somehow index it back to postgres. I wonder how that works conceptually / architecturally speaking
    - paulryanrogers 3mo ago
      Pg can do array columns, though I don't think it's a good fit for common use cases
    - zaptheimpaler 3mo ago
      The data is probably small enough and infrequently updated such that almost anything will work. If you split the items then you would have a separate episodes table with one row per episode joined to the podcasts table. If you store the whole XML in a row then you can overwrite the row when the feed changes. Doing the parsing and splitting into episodes in DB sounds better to me because your clients will otherwise constantly be repeating that work.
- SahAssar 3mo ago
  There is a datatype, if the XML is correct: https://www.postgresql.org/docs/current/datatype-xml.html https://www.postgresql.org/docs/current/datatype-xml.html

inigyou 3mo ago

A reader does things in realtime. You don't care what happened 6 months ago. If you did something 6 months ago you don't want to gaslight the user by pretending you did something different 6 months ago.