rdbms

I'm surprised this hasn't been posted yet. Any interesting tricks that you know about in Postgres? Obscure config options and scaling/perf tricks are particularly welcome. I'm sure we can beat the 9 comments on the corresponding MySQL thread :) tommym Since postgres is a lot more sane than MySQL, there are not that many "tricks" to report on ;-) The manual has some nice performance tips. A few other performance related things to keep in mind: Make sure autovacuum is turned on Make sure you've gone through your postgres.conf (effective cache size, shared buffers, work mem ... lots of options

In relation to my other question "What’s the best way to audit log DELETEs?" . What's the PostgreSQL equivalent of CONTEXT_INFO? [EDIT] I want to log deletes using trigger, but since i'm not using the database user as my app's logical user, I cannot log the CURRENT_USER from the trigger code as the user who deleted the record. But for INSERT and UPDATE it is possible to log the record changes from trigger since you can just add a user field in the record, say inserted_by and last_updated_by, and use these fields to log to audit table. Milen A. Radev http://www.postgres.cz/index.php/PostgreSQL

Just found out that Oracle does not like it when you use the AS keyword to alias a subquery: SELECT * FROM (SELECT * FROM products) AS p I need to keep my SQL queries as portable as possible. Will the removal of the AS keyword in the above query affect any other RDBMS? Jorge Campos The pattern for the SQL 99 ANSI is that the table can have an alias WITHOUT the AS keyword so, you can take out AS and it should work on every RDBMS. See it on fiddle: MySQL Oracle PostgreSql SQLLite SQLServer In ISO/IEC 9075-2:1999 , section 7.6 <table reference> , page 232: <table reference> ::= <table primary> |

We have different products that rely on relational databases for various reasons, basically the transactional nature of the operations (atomicity, consistency, etc.). This is not going to change any time soon. Given this scenario, are there any possible justifications to export the data to a NoSQL solution? Maybe Datawarehousing, Analytics, etc. Any comments are welcome. "Data" is just a vague generality without a data structure. "Relational" means the data structure is relations/tables with generic queries. ( Not automatically interleaved execution of semantically atomic concurrent

I have the following simple table: CREATE TABLE tbl_test ( id serial NOT NULL, poly polygon NOT NULL ) WITH (OIDS=FALSE); I then try to insert a row with a polygon: insert into tbl_test values(1, PolyFromText('POLYGON((0 0, 10 10, 10 0, 0 0))')) And run into this error: column "poly" is of type polygon but expression is of type geometry Which is lame. So my first questions is: Do I really have to cast? Anyway, after casting it works. And now I'm trying to do a simple ST_Contains query: select id, poly from tbl_test where ST_Contains(poly, Point(GeomFromText('POINT(9 2)'))) Which gives the