postgresql-9.4

I need to get as a result from query fully structured JSON. I can see in postgres that there are some built in functions that may be useful. As an example I created a structure as follows: -- Table: person -- DROP TABLE person; CREATE TABLE person ( id integer NOT NULL, name character varying(30), CONSTRAINT person_pk PRIMARY KEY (id) ) WITH ( OIDS=FALSE ); ALTER TABLE person OWNER TO postgres; -- Table: car -- DROP TABLE car; CREATE TABLE car ( id integer NOT NULL, type character varying(30), personid integer, CONSTRAINT car_pk PRIMARY KEY (id) ) WITH ( OIDS=FALSE ); ALTER TABLE car OWNER TO

I'm looking to migrate from Postgres 9.3 to 9.4, and have a lot of data in JSON columns. While it's fine, I wanted to have a look at migrating to the more efficient column storage (which JSONB seems to be — a really exciting piece of tech!). To actually migrate, I want to know migration characteristics for something like ALTER TABLE table_with_json ALTER COLUMN my_json SET DATA TYPE jsonb USING my_json::jsonb; (from this helpful question ). Ideally, it would be good to know how long it takes to migrate 1mil and 10mil entries, and how it scales. While I can get these numbers myself, I thought

I get a little confused some times when working with psql between when to use a set vs. \set vs. \pset . I think that: set is for session variables on my connection to the db. For example SET ROLE dba ; \set is for local variables for this psql session. For example \set time 'select current_timestamp' \pset is for psql settings for this psql session. For example '\pset border 2' But, I've never found what I thought was a good explanation of each. Are my assumptions above correct? I'm using PostgreSQL 9.4 Basically correct. The important difference is that SET is an SQL command while the other

Using JSON arrays in a jsonb column in Postgres 9.4 and Rails, I can set up a scope that returns all rows containing any elements from an array passed to the scope method - like so: scope :tagged, ->(tags) { where(["data->'tags' ?| ARRAY[:tags]", { tags: tags }]) } I'd also like to order the results based on the number of matched elements in the array. I appreciate I might need to step outside the confines of ActiveRecord to do this, so a vanilla Postgres SQL answer is helpful too, but bonus points if it can be wrapped up in ActiveRecord so it can be a chain-able scope. As requested, here's an

There are two tables: Authorized Contacts ( auth_contacts ): ( userid varchar contacts jsonb ) contacts contains an array of contacts with attributes {contact_id, type} discussion : ( contact_id varchar discussion_id varchar discussion_details jsonb ) The table auth_contacts has at least 100k records making it non JSONB type is not appropriate according as it would double or triple the amount of records. Sample data for auth_contacts : userid | contacts '11111' | '{"contact": [{"type": "type_a", "contact_id": "1-A-12"} , {"type": "type_b", "contact_id": "1-A-13"}]}' discussion table has 5

I have created a separate role "newrole" and new schema "newschema" for a certain user that should only execute some stored functions. I have managed to revoke access to schema "public" for the current database. Logged in as "newrole" I still have access to postgres database like this: SELECT * FROM pg_user I want to revoke all access to the postgres database and tried following that not work: REVOKE ALL ON DATABASE postgres FROM newrole When logged in as newrole I can still read the postgres database. How do I revoke any access to the postgres admin database? I have searched a long time but

Suppose that you want to store "tags" on your object (say, a post). With release 9.4 you have 3 main choices: tags as text[] tags as jsonb tags as text (and you store a JSON string as text) In many cases, 3rd would be out of question since it wouldn't allow query conditional to 'tags' value. In my current development, I don't need such queries, tags are only there to be shown on posts list, not to filter posts. So, choice is mostly between text[] and jsonb . Both can be queried. What would you use? And why? Erwin Brandstetter In most cases I would use a normalized schema with a table option