foo> - Search results in mailing lists
Mailing lists >> pgsql-docs >> Thread
2025-04-22 08:57:23 | Please clarify docs on user-defined settings for SET and RESET (PG Doc comments form)
foo.bar'); ERROR: unrecognized configuration parameter "foo.bar" postgres=# select current_setting('foo.bar', true
Mailing lists >> pgsql-docs >> Thread
2025-03-20 17:08:50 | Re: Ambiguity in IS JSON description and logic (Kirk Parker)
foo(js); A couple of side notes: 1. Your first data example is not JSON
Mailing lists >> pgsql-docs >> Thread
2024-12-03 02:55:30 | 34.3.2. Using Cursors (PG Doc comments form)
foo_bar CURSOR FOR SELECT number, ascii FROM foo ORDER BY ascii; EXEC SQL OPEN
Mailing lists >> pgsql-docs >> Thread
2024-10-22 11:12:01 | "5.3. Identity Columns" Incorrect Usage of "VALUE" in Documentation (PG Doc comments form)
foo'); INSERT INTO people (name, address) VALUES ('B', 'bar'); I recommend updating the documentation to correct
Mailing lists >> pgsql-docs >> Thread
2024-09-03 18:10:57 | Re: Table rewrite supporting functions for event triggers (Greg Sabino Mullane)
foo set unlogged, alter id type bigint; But I wrote it wrong: they should be 1,2,4,8. Cheers
Mailing lists >> pgsql-docs >> Thread
2024-07-22 08:00:26 | Undocumented := alternative in using option of raise statement (PG Doc comments form)
foo'; end $$;" works and the alternative to "=" is documented in https:///docs/current/plpgsql-statements.html#PLPGSQL-STATEMENTS-ASSIGNMENT I suggest to change
Mailing lists >> pgsql-docs >> Thread
2024-05-04 17:52:21 | Re: RETURNING order guarantees documentation (Tom Lane)
foo set ... returning *) select * from upd order by ...; Otherwise it's going to be the order
Mailing lists >> pgsql-docs >> Thread
2024-03-14 00:16:07 | Locking (PG Doc comments form)
foo into f from bar where id=1; f = f + 123; update bar set foo = f where
Mailing lists >> pgsql-docs >> Thread >> Search in thread (2)
2023-12-19 11:07:47 | Re: 'bar' shouldn't be a string in example (Daniel Gustafsson)
foo '1', drop 'bar'); ALTER FOREIGN DATA WRAPPER postgres=# select fdwoptions from pg_foreign_data
Mailing lists >> pgsql-docs >> Thread >> Search in thread (2)
2023-10-16 16:29:09 | Re: "20.16. Customized Options" – cannot be set by `ALTER SYSTEM` (Tom Lane)
foo.bar TO 'baz'; ERROR: unrecognized configuration parameter "foo.bar" regression=# SET foo.bar TO 'baz'; SET regression
Mailing lists >> pgsql-docs >> Thread
2023-09-05 09:36:45 | Clarification of deadlock possibilities in section 13.3.5. Advisory Locks (PG Doc comments form)
foo WHERE id > 12345 ORDER BY id ASC LIMIT 100 ) q; -- ok Can you clarify
Mailing lists >> pgsql-docs >> Thread
2023-03-31 12:35:55 | Re: Minor typo in 13.3.5. Advisory Locks (Tom Lane)
foo WHERE id > 12345 LIMIT 100; -- danger! This might cause some locks to be acquired
Mailing lists >> pgsql-docs >> Thread
2022-11-03 17:40:50 | Re: Missing documentation (Alvaro Herrera)
foo=bar" in the URI, but both the whitespace and the second equals sign need
Mailing lists >> pgsql-docs >> Thread
2022-09-16 18:57:25 | Clarifying docs on nuance of select and update policies (Chandler Gonzales)
foo enable row level security; grant select on table foo to some_user_type; grant
Mailing lists >> pgsql-docs >> Thread
2022-07-14 12:01:48 | Re: Clarify the ordering guarantees in combining queries (or lack thereof) (Tom Lane)
foo union all select * from foo; QUERY