| Replied (other)Follow-up patch | create table explicitly mention that unique|primary key constraint will create an | about 2 years ago |
| Replied (other)Follow-up patch | BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key | about 2 years ago |
| Replied (other)Follow-up patch | BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key | about 2 years ago |
| Replied (other)First patch | SQL command : ALTER DATABASE OWNER TO | about 2 years ago |
| Replied (other)First patch | BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key | about 2 years ago |
| Replied (other) | No title | about 2 years ago |
| Replied (other) | It would be nice to clarify is there any point in select queries pipelining | about 2 years ago |
| Replied (other) | SQL command : ALTER DATABASE OWNER TO | about 2 years ago |
| Replied (other) | BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment | about 2 years ago |
| Replied (other) | SQL command : ALTER DATABASE OWNER TO | about 2 years ago |
| Replied (other) | SQL command : ALTER DATABASE OWNER TO | about 2 years ago |
| Replied (other) | BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment | about 2 years ago |
| Replied (other) | BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key | about 2 years ago |
| Started thread | Spam complaint | about 2 years ago |
| Replied (other) | SQL command : ALTER DATABASE OWNER TO | about 2 years ago |
| Replied (other) | psql JSON output format | about 2 years ago |
| Replied (other) | psql JSON output format | about 2 years ago |
| Replied (other) | psql JSON output format | about 2 years ago |
| Replied (other) | Reordering DISTINCT keys to match input path's pathkeys | about 2 years ago |