Seems reasonable, I have not personally used vertica, but judging by the queries it seems pretty straightforward.

I presume we can use a docker container, such as:

https://hub.docker.com/r/vertica/vertica-ce

I was able to get the container to work with a few modifications to reduce the startup time:

• setting VMART_ETL_SCRIPT env variable to empty string to prevent loading VMART schema
• mounting empty folder over /opt/vertica/packages to prevent additional package installation steps

Only one instance of Vertica can be running on a host at any time so I put all assertions into one unit test.

@mfridman I'd love to see this merged. Any concerns on your end?

No concerns with the PR itself, more concern about the ongoing maintenance.

I'm not familiar with vertica DB, so if users start filing issues/ask questions there is an additional maintenance cost to the current and future maintainers.

I'm starting to think there might be "official" and "third-party" goose support for the various databases and drivers.

What do you think about instead of this PR just exporting the functions on the SQLDialect interface so it can be implemented outside the goose package and offering something like:

func SetDialectThirdParty(d SQLDialect) {
	dialect = d
}

What do you think about instead of this PR just exporting the functions on the SQLDialect interface so it can be implemented outside the goose package and offering something like:

Interesting idea, but that would mean you could only use it from the golang API right, and the cli would not work?

Hey @bobpace, if you're up for it, can you rebase (or merge) main, overall looks good to me and we can merge this in.

That sounds great, thanks!