S3 doesn't support continual logging - you need to decide on a file size up-fron... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		bdonlan on Nov 23, 2011 \| parent \| context \| favorite \| on: Heroku Postgres: SQL Database-as-a-Service S3 doesn't support continual logging - you need to decide on a file size up-front. Are you creating a new object for each log entry, or is there a window in which commits can be lost before the log gets flushed out, or do you have some other workaround...?

joevandyk on Nov 23, 2011 [–]

There's a window of a couple minutes in which data could be lost (in the worst case scenario).

sector on Nov 23, 2011 | [–]

So it's postgres log shipping, with S3 as the target?

joevandyk on Nov 23, 2011 | | [–]

Yup.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact