I would do smth like:
SELECT format( 'ALTER SYSTEM SET shared_preload_libraries = %L;', setting )
FROM pg_settings WHERE name = 'shared_preload_libraries' \gexec
Of course, you should add new value to the existing setting, making sure
there are no duplicates and the format is correct.
--
Victor Yegorov
> But I want it to do this (note that "500" is quoted):
>
> select row_to_json(row(500::bigint));
> row_to_json
> -
> {"f1":"500"}
>
Will this work?
select row_to_json(row(500::text));
--
Victor Yegorov
eems not
to.
I assume there's smth to do with implicit BEGIN issued in non-AUTOCOMMIT
mode and non-atomic DO block behaviour.
--
Victor Yegorov
f_print_x() >> x=0
DO
I don't understand why CALL statement is not seeing an updated record.
With AUTOCOMMIT=on, all goes as expected.
I tried to examine snapshots and xids (commented lines), but they're always
the same.
Can you explain this behavior, please? Is it expected?
--
Victor Yegorov
I:SS"
ALTER SESSION SET nls_date_format='-MM-DD HH24:MI:SS';
Otherwise, you have to load this CSV file in a table, that has `text` type
for the column and do a post-processing,
smth like:
INSERT INTO permanent_tab
SELECT *, to_timestamp(col, 'DD-MON-YY HH12.MI.SS.S AM') FROM
temp_table;
Hope this helps.
--
Victor Yegorov
сб, 27 февр. 2021 г. в 01:51, Stacey Haysler :
> If you have any comments or suggestions for the translation, please bring
> them to our attention no later than 5:00 PM PST on Friday, March 5, 2021.
>
Greetings.
I looked through the text and made some comments.
--
Victo
witch, any remaining entries can be moved from previous to the
live table (shouldn't be necessary if switch is done properly, although
might be tricky in a presence of a long transactions)
- previous table is TRUNCATEd
In your case, you can do `VACUUM FULL` between replicating each batch of
tables.
--
Victor Yegorov
чт, 6 февр. 2020 г. в 04:55, Vik Fearing :
> Please answer +1 if you want or don't mind seeing transaction status by
> default in psql or -1 if you would prefer to keep the current default.
>
+1
--
Victor Yegorov
;
If you see `ALTER DEFAULT PRIVILEGES … REVOKE …` and want to undo it, you
will have to GRANT corresponding privilege.
--
Victor Yegorov
that will show you
internal queries used for displaying this information, or you can `\set
ECHO_HIDDEN on` with the same effect.
Also, you can do `pg_dumpall -s | grep -E 'DEFAULT PRIVILEGE|\\connect' and
it'll produce a list of all entries for all databases, along with database
name.
--
Victor Yegorov
2017-12-22 2:03 GMT+02:00 David G. Johnston :
> On Thu, Dec 21, 2017 at 4:53 PM, Victor Yegorov
> wrote:
>
>> postgres=# select except select;
>> --
>> (2 rows)
>> postgres=# select intersect all select;
>> --
>> (2 rows)
>
postgres=# select intersect all select;
--
(2 rows)
Why is it so?
Should this be reported as a bug?.. ;)
--
Victor Yegorov
12 matches
Mail list logo
