pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Lian Jiang <jiangok2006@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: speed up full table scan using psql
Date: Wed, 31 May 2023 14:43:09 -0700
Message-ID: <d6b0d93a-e0fe-c92a-bec1-1f4de5627952@aklaver.com> (raw)
In-Reply-To: <CA+aY8X4Wn2KBDYsqspPOoWUybsB1Jh6yfBVChMSHxVkuRVm3VQ@mail.gmail.com>
References: <CA+aY8X6E6qq-i_10G_wTjkorEtm3XYW+Ag+83xk7gmJUoAoing@mail.gmail.com>
	<c4bfbccc-b004-5830-ade9-c1a12db91e8a@aklaver.com>
	<CA+aY8X4Wn2KBDYsqspPOoWUybsB1Jh6yfBVChMSHxVkuRVm3VQ@mail.gmail.com>

On 5/31/23 13:57, Lian Jiang wrote:
> The command is: psql $db_url -c "copy (select row_to_json(x_tmp_uniq) 
> from public.mytable x_tmp_uniq) to stdout"
> postgres version:  14.7
> Does this mean COPY and java CopyManager may not help since my psql 
> command already uses copy?

I don't think the issue is COPY itself but row_to_json(x_tmp_uniq).

This:

https://towardsdatascience.com/spark-essentials-how-to-read-and-write-data-with-pyspark-5c45e29227cd

indicates Spark can use CSV as an input source.

Given that I would just COPY the data out as CSV.

> 
> Regarding pg_dump, it does not support json format which means extra 
> work is needed to convert the supported format to jsonl (or parquet) so 
> that they can be imported into snowflake. Still exploring but want to 
> call it out early. Maybe 'custom' format can be parquet?
> 
> 
> Thanks
> Lian

-- 
Adrian Klaver
adrian.klaver@aklaver.com






view thread (12+ messages)  latest in thread

Message-ID: <d6b0d93a-e0fe-c92a-bec1-1f4de5627952@aklaver.com>
Permalink:  ../d6b0d93a-e0fe-c92a-bec1-1f4de5627952@aklaver.com/
Also on:    postgresql.org/message-id/d6b0d93a-e0fe-c92a-bec1-1f4de5627952@aklaver.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: adrian.klaver@aklaver.com, jiangok2006@gmail.com
  Subject: Re: speed up full table scan using psql
  In-Reply-To: <d6b0d93a-e0fe-c92a-bec1-1f4de5627952@aklaver.com>
  References: <CA+aY8X6E6qq-i_10G_wTjkorEtm3XYW+Ag+83xk7gmJUoAoing@mail.gmail.com> <c4bfbccc-b004-5830-ade9-c1a12db91e8a@aklaver.com> <CA+aY8X4Wn2KBDYsqspPOoWUybsB1Jh6yfBVChMSHxVkuRVm3VQ@mail.gmail.com> <d6b0d93a-e0fe-c92a-bec1-1f4de5627952@aklaver.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox