Thanks for contributing to pgloader by reporting an
issue! Reporting an issue is the only way we can solve problems, fix bugs,
and improve both the software and its user experience in general.

The best bug reports follow those 3 simple steps:

1. show what you did : Tried migrating the data from MS SQL to POstgres
2. show the result you got :
3. tmpdir: #P"/tmp/pgloader/"
   2022-08-18T16:29:50.011000Z NOTICE Starting pgloader, log system is ready.
   2022-08-18T16:29:50.028000Z INFO Starting monitor
   2022-08-18T16:29:50.032000Z LOG pgloader version "3.6.1"
   2022-08-18T16:29:50.032000Z INFO SOURCE: "mssql://sa:XXX1@LAPTOP-5H:1433/gcpmigrationajay"
   2022-08-18T16:29:50.033000Z INFO SOURCE URI: #<PGLOADER.SOURCE.MSSQL:MSSQL-CONNECTION mssql://sa@LAPTOP-5HJ:1433/gcpmigrationajay {1005D78713}>
   2022-08-18T16:29:50.033000Z INFO TARGET: "pgsql://postgres:XXX1@127.0.0.1:5435/postgres"
   2022-08-18T16:29:50.034000Z INFO TARGET URI: #<PGLOADER.PGSQL:PGSQL-CONNECTION pgsql://postgres@127.0.0.1:5435/postgres {1005F9A793}>
   2022-08-18T16:29:50.034000Z DEBUG LOAD DATA FROM #<PGLOADER.SOURCE.MSSQL:MSSQL-CONNECTION mssql://sa@LAPTOP-5HJQKLNN:1433/gcpmigrationajay {1005D78713}>
   2022-08-18T16:29:50.098000Z DEBUG CONNECTED TO #<PGLOADER.PGSQL:PGSQL-CONNECTION pgsql://postgres@127.0.0.1:5435/postgres {1005F9A793}>
   2022-08-18T16:29:50.099000Z DEBUG SET client_encoding TO 'utf8'
   2022-08-18T16:29:50.099000Z DEBUG SET application_name TO 'pgloader'
   2022-08-18T16:29:50.118000Z LOG Migrating from #<MSSQL-CONNECTION mssql://sa@LAPTOP-5HJ:1433/gcpmigrationajay {1005D78713}>
   2022-08-18T16:29:50.119000Z LOG Migrating into #<PGSQL-CONNECTION pgsql://postgres@127.0.0.1:5435/postgres {1005F9A793}>
   Max connections reached, increase value of TDS_MAX_CONN

2022-08-18T16:29:50.328000Z INFO Stopping monitor

What I am doing here?

There is no applicable method for the generic function
#<STANDARD-GENERIC-FUNCTION PGLOADER.PGSQL:ADJUST-DATA-TYPES (2)>
when called with arguments
(#S(PGLOADER.CATALOG:CATALOG
:NAME "gcpmigrationajay"
:SCHEMA-LIST NIL
:TYPES-WITHOUT-BTREE NIL
:DISTRIBUTION-RULES NIL)
NIL).
See also:
The ANSI Standard, Section 7.6.6
4. explain how the result is not what you expected. : Connection was successful on postgres. But while connecting MS SQL it has failed

In the case of pgloader, here's the information I will need to read in your
bug report. Having all of this is a big help, and often means the bug you
reported can be fixed very efficiently as soon as I get to it.

Please provide the following information:

• pgloader --version:
  pgloader version "3.6.1"
  compiled with SBCL 1.4.15.debian

  <fill pgloader version here>
  

• did you test a fresh compile from the source tree? Yes

  Compiling pgloader from sources is documented in the
  README, it's
  easy to do, and if patches are to be made to fix your bug, you're going
  to have to build from sources to get the fix anyway…

• did you search for other similar issues?

• how can I reproduce the bug? : You could have a MS SQL 2016 and postgres 12 version and try to migrate the data. I got this error after several attempts. Few attempts were failed initially due to incorrect password.

  Incude a self-contained pgloader command file.

  If you're loading from a database, consider attaching a database dump to
  your issue. For MySQL, use mysqldump. For SQLite, just send over your
  source file, that's easy. Maybe be the one with your production data, of
  course, the one with just the sample of data that allows me to reproduce
  your bug.

  When using a proprietary database system as a source, consider creating
  a sample database on some Cloud service or somewhere you can then give
  me access to, and see my email address on my GitHub profile to send me
  the credentials. Still open a public issue for tracking and as
  documentation for other users.

• pgloader output you obtain : Mentioned in point 2

PASTE HERE THE OUTPUT OF THE PGLOADER COMMAND
2022-08-18T16:51:44.046000Z LOG pgloader version "3.6.1"
2022-08-18T16:51:44.180000Z LOG Migrating from #<MSSQL-CONNECTION mssql://sa@LAPTOP-5HJ:1433/gcpmigrationajay {1005D80713}>
2022-08-18T16:51:44.181000Z LOG Migrating into #<PGSQL-CONNECTION pgsql://postgres@127.0.0.1:5435/postgres {1005ECAA13}>
Max connections reached, increase value of TDS_MAX_CONN
KABOOM!
FATAL error: There is no applicable method for the generic function
               #<STANDARD-GENERIC-FUNCTION PGLOADER.PGSQL:ADJUST-DATA-TYPES (2)>
             when called with arguments
               (#S(PGLOADER.CATALOG:CATALOG
                   :NAME "gcpmigrationajay"
                   :SCHEMA-LIST NIL
                   :TYPES-WITHOUT-BTREE NIL
                   :DISTRIBUTION-RULES NIL)
                NIL).
See also:
  The ANSI Standard, Section 7.6.6
An unhandled error condition has been signalled:
   There is no applicable method for the generic function
     #<STANDARD-GENERIC-FUNCTION PGLOADER.PGSQL:ADJUST-DATA-TYPES (2)>
   when called with arguments
     (#S(PGLOADER.CATALOG:CATALOG
         :NAME "gcpmigrationajay"
         :SCHEMA-LIST NIL
         :TYPES-WITHOUT-BTREE NIL
         :DISTRIBUTION-RULES NIL)
      NIL).
See also:
  The ANSI Standard, Section 7.6.6


  - [ ] data that is being loaded, if relevant
  

PASTE HERE THE DATA THAT HAS BEEN LOADED

  - [ ] How the data is different from what you expected, if relevant