Search Results

\timing is a psql command - that is, it acts on the client side. If you want to know the timing of your queries on the server side (that is, written to the logs), do SET log_min_duration_statement TO …

I have created a small test for checking this: CREATE TABLE jsonb_test (id serial, data jsonb); Then inserted some generated data: INSERT INTO jsonb_test (data) SELECT row_to_json(x.*)::jsonb …

It seems you are after the percentile_disc() ordered-set aggregate function. The documentation says the following about it: percentile_disc(fraction) WITHIN GROUP (ORDER BY sort_expression) discrete …

There are multiple levels where you configuration options are set in PostgreSQL: system defaults values specified in postgresql.conf or the startup command line values preset for a database, user (m …

The actions taken in the trigger are part of the transaction that fires it. This means that the counter increment will happen only if the whole transaction (or the subtransaction defined by a SAVEPOI …

Let's simply try it! I've created the table from your question, then did the following: INSERT INTO mytable SELECT json_object(ARRAY['myfield', i::text || 'bla'])::jsonb FROM generate_series (1, 1 …

Let's create a function that has a side effect so that we can see how many times it is executed: CREATE OR REPLACE FUNCTION test.this_here(val integer) RETURNS numeric LANGUAGE plpgsql AS $fu …

As it sounds, you are in a split brain situation. The original master (01) was never stopped from being master, and after the promotion of 02, it became just another master. Fixing such issues pre-9 …

The thing is that here you have to combine two literals: '{}' for the array and '[...,...]' for the range type. In all these cases, the easiest is just getting back the output from the system itself: …

It looks like indzone is a varchar(20), not a text - you could either specify the returned record using the former, or cast indzone inside the function. (This applies to the solution suggested below, …

According to the documentation, what one needs for creating tables in a schema is CREATE on that schema. This you think you revoked, but as you experience it didn't really happen - the only plausible …

Just a slight variation to Chris's answer: SELECT a, translate(b, '[]', '{}')::text[] AS b, d FROM json_to_record('{"a": 1, "b": ["hello", "There"], "c": "bar"}') AS x(a int, b text, d text); The i …

The privileges are not automatically removed. Let's consult the documentation, as always: dropping a role is often not just a matter of a quick DROP ROLE. Any objects owned by the role must first …

Here is a small example to prove my point: CREATE TABLE some_data ( data hstore ); INSERT INTO some_data VALUES ('a=>bla'), ('access=>bla'), ('access=>user'); Now taking your JSO …

If you stop your database, it is safe to remove the log file (unless you need it for checking something later, so it is probably better to back it up somehow). Upon restart, an empty file will be cre …