From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
---|---|
To: | "Andy Hartman" <hartman60home(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Display Bytea field |
Date: | 2025-01-10 12:49:40 |
Message-ID: | 1309d698-fa5f-493e-809a-fd6d95d913b6@manitou-mail.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Andy Hartman wrote:
> How thru a simple query can I make sure data matches and I can display it
>
> On Thu, Jan 9, 2025 at 3:16 PM Andy Hartman <hartman60home(at)gmail(dot)com> wrote:
>
> > I have migrated over a Table from Mssql that had an Image column I now
> > have it in Postgres
Within psql, the bytea field can be copied into a large object
with lo_from_bytea() [1], and then the large object exported
into a local file with \lo_export [2]
Alternatively, you could compare image checksums before and
after moving them into postgres. The advantage is that you
don't need to export or view any file, and you compare globally
all your images. If the checksums are identical, the data are identical.
On the MSSQL side, checksums can be computed with hashbytes()
as suggested in this stackoverflow answer: [3]
On the postgres side, use functions like md5() or sha256()
directly on the bytea column.
[1] https://www.postgresql.org/docs/current/lo-funcs.html
[2]
https://www.postgresql.org/docs/current/app-psql.html#APP-PSQL-META-COMMAND-LO-EXPORT
[3] https://stackoverflow.com/a/33256990/
Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2025-01-10 14:39:10 | Re: Display Bytea field |
Previous Message | shammat | 2025-01-10 10:44:29 | Re: Postgres do not support tinyint? |