title: Timezone issues with Redshift COPY from Parquet
body: <p>I am loading a Parquet file into Redshift.  The Parquet file has a timestamp column.  </p>
  
  <p>Question: Is there any way to specify what timezone to use as context when converting the Parquet timestamp (a specific instant in time) to a <code>TIMESTAMP</code> in Redshift (an abstract date/time without timezone context)</p>
  
  <p>Put differently:</p>
  
  <p>When I INSERT <code>'2019-01-01 00:00'::timestamp</code> into a <code>TIMESTAMP</code> column, I get exactly <code>2019-01-01 00:00</code> back, no matter what my session timezone is.  I would imagine CSV is similar. </p>
  
  <p>When I load from Parquet, the only way I can get <code>2019-01-01 00:00</code> into a <code>TIMESTAMP</code> column is if the Parquet timestamp represents <code>2019-01-01 00:00 _UTC_</code>.    I would like to get the same result in Redshift with a timestamp like  <code>2019-01-01 00:00 _EDT_</code> in Parquet (which would be <code>04:00</code> or <code>05:00</code> UTC)</p>