>>>>> On Mon, 29 Aug 2022 08:28:31 +0200, Uwe Schuerkamp said: > Mail-Followup-To: Uwe Schuerkamp <uwe.schuerk...@bertelsmann.de>, > > On Thu, Aug 25, 2022 at 06:57:46PM +0100, Martin Simmons wrote: > > Do you have non-ASCII characters in your volume, job or client names? If > > not, > > then I don't see why the warning would cause them to look quite funny > > (whatever that means). > > > > __Martin > > Hi folks, > > thanks for your answers. No, I don't have any non-ascii chars in my > client, job or volume names. By "looking funny" I mean that for > instance the disk volume name "zif-full-0001" turns into > \xverlongrowofrandomcharacters. > > Of course I could start with an empty catalog but it'd be nice to > transfer the existing history to the postgres db which I guess would > (or should, even) be possible somehow. In another experiment I > migrated a mariadb django backend to postgresql on the same machine > without any issues, it's just bacula that's acting up in this case.
Bacula will probably not work if pgloader created the schema. I think you should do that part with Bacula's make_postgresql_tables script and configure pgloader to keep that schema (i.e. the opposite of most of the "WITH" clauses that you mentioned originally. Many of the fields in Bacula's mysql schema use BLOB types. The doc for pgloader says that blob is converted to the bytea type in postgresql, so I don't know if that will cause translation problems after using make_postgresql_tables. You might need to configure pgloader's type conversion rules. __Martin _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
