Yes, that's what I meant. With the default casts, pgloader will convert those fields to binary and use hex-encoded strings in the SQL (https://www.postgresql.org/docs/current/datatype-binary.html#id-1.5.7.12.9). Since the actual PostgreSQL field type is text, the encoded strings are then inserted directly into the database as seen in the output of list jobs etc.
__Martin >>>>> On Thu, 1 Sep 2022 10:24:30 -0300, Wanderlei Huttel said: > > Hello Uwe > > I found a document on the internet about pgloader. > Maybe it would be necessary to make a cast of the fields. > > https://pgloader.readthedocs.io/en/latest/ref/mysql.html#mysql-database-casting-rules > > > Best regards > > *Wanderlei Hüttel* > > > > Em qui., 1 de set. de 2022 às 10:00, Uwe Schuerkamp < > uwe.schuerk...@nionex.net> escreveu: > > > On Thu, Sep 01, 2022 at 01:01:31PM +0100, Martin Simmons wrote: > > > > > The volume name above is "zif-incr-0019" if you decode the hex, so it > > looks > > > like you need to add some translation from the various BLOB types to > > text in > > > the pgloader configuration if that is possible. By default, pgloader > > converts > > > the BLOB types to binary. > > > > > > > Hello Martin et al., > > > > I just checked the table definition in postgres (as it's created by > > bacula's script) and the fields in question are all of type "text" in > > postgres, not binary, even after pgloader has imported the mysql data. > > > > I may well be mis-interpreting psql's output, but this is what I > > see when I look at the job table for instance: > > > > \d+ job > > Table > > "public.job" > > Column | Type | Collation | Nullable | > > Default | Storage | Stats target | Description > > > > -----------------+-----------------------------+-----------+----------+------------------------------------+----------+--------------+------------- > > jobid | integer | | not null | > > nextval('job_jobid_seq'::regclass) | plain | | > > job | text | | not null | > > | extended | | > > name | text | | not null | > > | extended | | > > > > > > So I'm wondering why "text" would end up displayed as "hex" in bconsole? > > > > Thanks again for your help (and your patience with a postgres noob :-)), > > > > Uwe > > > > > > -- > > Uwe Schürkamp // email: <uwe.schuerk...@bertelsmann.de> > > > > > > > > > > > > _______________________________________________ > > Bacula-users mailing list > > Bacula-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
