postgresql-9.3

I have to calculate my products stock cost, so for every product after each buy, i have to recalculate the Weighted Average Cost . I got a view thats bring me the current product's stock after each in/out: document_type document_date product_id qty_out qty_in price row_num stock_balance SI 01/01/2014 52 0 600 1037.28 1 600 SI 01/01/2014 53 0 300 1357.38 2 300 LC 03/02/2014 53 100 0 1354.16 3 200 LC 03/02/2014 53 150 0 1355.25 4 50 LC 03/02/2014 52 100 0 1035.26 5 500 LC 03/02/2014 52 200 0 1035.04 6 300 LF 03/02/2014 53 0 1040 1356.44 7 1090 LF 03/02/2014 52 0 1560 1045 8 1860 LC 04/02/2014 52

I have a sequence on postgresql 9.3 inside a schema. I can do this: SELECT last_value, increment_by from foo."SQ_ID"; last_value | increment_by ------------+-------------- 1 | 1 (1 fila) but this not Works: SELECT nextval('foo.SQ_ID'); ERROR: no existe la relación «foo.sq_id» LÍNEA 1: SELECT nextval('foo.SQ_ID'); What is wrong ? It says that not exist the relation «foo.sq_id», but it exists. The quoting rules are painful. I think you want: SELECT nextval('foo."SQ_ID"'); to prevent case-folding of SQ_ID . SELECT last_value, increment_by from "other_schema".id_seq; for adding a seq to a column

Current Postgresql versions have introduced various features for JSON content, but I'm concerned if I really should use them - I mean, there is not yet "best practice" estabilished on what works and what doesn't, or at least I can't find it. I have a specific example - I have a table about objects which, among other things, contains a list of alternate names for that object. All that data will also be included in a JSON column for retrieval purposes. For example (skipping all the other irrelevant fields). create table stuff (id serial primary key, data json); insert into stuff(data) values('{

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

I have two tables in a Postgresql 9.3 database, companies and sites. There is a one-to-many relationship between them with companies on the one side. There is a foreign key constraint that prevents the deletion of a company if sites have been assigned to it. If I attempt to delete the company with the ID 'KSL' using an SQL query directly on the database, I get the expected error: ERROR: update or delete on table "companies" violates foreign key constraint "sites_company_id_fkey" on table "sites" DETAIL: Key (company_id)=(KSL) is still referenced from table "sites". I have defined an artisan