Jeremy Finzel

@eulerto this would be really useful. What would it take to get this tested and merged?

+1 for this feature. On really busy OLTP systems it's extremely likely to hit `lock_timeout`, but just as likely that within 5 minutes of brief retries you will indeed get...

@marcotollini thanks for the input. This is similar to our own workaround which is to do no conversions at all on raw data but only through views using postgres built-in...

I am very interested in this functionality. I understand the problem with integration testing, however, the connector developed by Snowflake only loads the raw message data, which leaves many problems...

Thank you both so much for the feedback. @ringerc I definitely didn't capture core files. I will keep that in mind for future. I found this in the provider logs...

@PJMODOS thanks much for the feedback. As you see I posted an issue on their repo. It's a nice extension so hopefully we will see progress on this.

@PJMODOS @dvarrazzo it has been 2 years since this happened, I'm actually still not convinced this has anything to do with pg_repack. I am convinced the only reason above issue...

Also, with parallel plans, the worker nodes are summed up to create a much higher duration than is actual.

I'm not sure this feature would be helpful. It is easy enough to figure out the difference between reads and writes and say "Therefore, I don't want to index this...

I'm not suggesting ignoring write activity, but I am suggesting that I hesitate to ignore read activity. For situations like you describe, I think the right solution is to be...