1. In postgresql create the test_d table by the following script: create table test.test_d (d integer ); insert into test.test_d (d) values (3); insert into test.test_d (d) values (1); insert into test.test_d (d) values (3); 2. Add postgresql database configuration in standalone-teiid.xml <datasource jndi-name= "java:/test_pg" pool-name= "test_pg" enabled= "true" use-java-context= "true" > <connection-url> jdbc:postgresql://localhost:5432/test?charSet=utf8 </connection-url> <driver-class> org.postgresql.Driver </driver-class> <driver> org.postgresql </driver> <pool> <min-pool-size> 2 </min-pool-size> <max-pool-size> 70 </max-pool-size> <prefill> false </prefill> <use-strict-min> false </use-strict-min> <flush-strategy> FailingConnectionOnly </flush-strategy> </pool> <security> <user-name> postgres </user-name> <password> xxxxxx </password> </security> <validation> <check-valid-connection-sql> select 0 </check-valid-connection-sql> </validation> <timeout> <blocking-timeout-millis> 120000 </blocking-timeout-millis> <idle-timeout-minutes> 5 </idle-timeout-minutes> </timeout> </datasource> 3. Add in test-vdb.xml java:/test_pg configured in previous step as datasource: <model name= "test_pg" > <property name= "importer.useFullSchemaName" value= "false" /> <property name= "importer.tableTypes" value= "TABLE,VIEW" /> <property name= "importer.importKeys" value= "false" /> <source name= "test_pg" translator-name= "myPg" connection-jndi-name= "java:/test_pg" /> </model> 4. Configure in test-vdb.xml the following virtual view: <model visible = "true" type = "VIRTUAL" name = "views" > <metadata type = "DDL" > <![CDATA[ CREATE virtual view test_d (d integer) as select 3 union all select 1 union all select 3 ]]> </metadata> </model> 5. Running the following query: with mytab as ( select d>2 as col1 FROM "views.test_d" ) select * from mytab where col1 = true ;; will return correct results: col1 ------ true true 6. Running the following query: with mytab as ( select d>2 as col1 FROM "test_pg.test_d" ) select * from mytab where col1 = true ;; will fail with the error message mentioned in description of the issue. But running the same query on PostgreSQL 9.3 will work fine, without any exceptions showing the same results as in 5 step. The behavior can be related to changes listed in https://www.postgresql.org/docs/9.6/static/release-9-5.html , especially because of it: Adjust operator precedence to match the SQL standard (Tom Lane) > The precedence of <=, >= and <> has been reduced to match that of <, > and =. The precedence of IS tests (e.g., x IS NULL) has been reduced to be just below these six comparison operators. Also, multi-keyword operators beginning with NOT now have the precedence of their base operator ( for example, NOT BETWEEN now has the same precedence as BETWEEN) whereas before they had inconsistent precedence, behaving like NOT with respect to their left operand but like their base operator with respect to their right operand. The new configuration parameter operator_precedence_warning can be enabled to warn about queries in which these precedence changes result in different parsing choices.