postgres support 3 part id

[dlawin]

Similar change for postgres as:
#13
#16

[erezsh]

When does postgres support 3 part table paths? Can you include a test for this?

[dlawin]

When does postgres support 3 part table paths? Can you include a test for this?

All of the providers with 3 part support so far allow you to use 1, 2, or 3 part ids. When using 2 or 3 parts, you are overriding the default "schema" and/or "database". Although these namespaces are referred to differently sometimes

[erezsh]

Looks good enough!

Just one small change if you please - no need to create a new decorator. Instead just use @test_each_database along with @skipIf if the db is within the set of dbs. Because in a future refactor, we're going to use something like db.max_path_len >= 3.

[dlawin]

Looks good enough!

Just one small change if you please - no need to create a new decorator. Instead just use @test_each_database along with @skipIf if the db is within the set of dbs. Because in a future refactor, we're going to use something like db.max_path_len >= 3.

Wasn't quite sure on how to implement with the decorator, but I added an if statement instead