There is a small but eye catching glitch in the v12 (and master) docs
for "CREATE TABLE AS".
https://www.postgresql.org/docs/12/sql-createtableas.html
index b5c4ce6959..56d06838f1 100644
--- a/doc/src/sgml/ref/create_table_as.sgml
+++ b/doc/src/sgml/ref/create_table_as.sgml
@@ -146,7 +146,6 @@
On 31.03.2019, 04:35 Andres Freund wrote:
>
> > bool
> > -CountOtherDBBackends(Oid databaseId, int *nbackends, int *nprepared)
> > +CountOtherDBBackends(Oid databaseId, int *nbackends, int *nprepared, bool
> > force_terminate)
> > {
>
> That doesn't seem like a decent API to me.
Only excuse i
implemented, so this is *not* a
performance improvement. Only a little more flexibility.
On Sat, Mar 9, 2019 at 3:31 AM Thomas Munro wrote:
>
> On Fri, Mar 8, 2019 at 1:37 PM Filip Rembiałkowski
> wrote:
> > See attached patch... I'm ready to work on so it can get merged
Thank you. Updated patch attached.
On Sat, Mar 9, 2019 at 2:53 AM Thomas Munro wrote:
>
> On Wed, Mar 6, 2019 at 1:39 PM Filip Rembiałkowski
> wrote:
> > Here is Pavel's patch rebased to master branch, added the dropdb
> > --force option, a test case
gt;
> > On 2/20/16 8:00 AM, Filip Rembiałkowski wrote:
> >> On Fri, Feb 19, 2016 at 10:09 PM, Catalin Iacob >> On 2/9/16, Tom Lane mailto:t...@sss.pgh.pa.us>>
> >> wrote:
> >> > FWIW, I think it would be a good thing if the NOTIFY st
Good day.
Sorry to pop in, but if you are active users of ltree, please let me
know if you rely on the exclamation operator (negative matching)?
I have just filed a patch, fixing very old bug - and it changes the
logic substantially.
https://commitfest.postgresql.org/23/2054/ - I'd be grateful fo
Hi all,
Here is my attempt to fix a 12-years old ltree bug (which is a todo item).
I see it's not backward-compatible, but in my understanding that's
what is documented. Previous behavior was inconsistent with
documentation (where single asterisk should match zero or more
labels).
http://archive
Marti Raudsepp wrote:
>
> Hi
>
> > út 18. 12. 2018 v 16:11 odesílatel Filip Rembiałkowski
> > napsal:
> >> Please share opinions if this makes sense at all, and has any chance
> >> going upstream.
>
> Clearly since Pavel has another implementation of
Hi,
I propose a simple patch (works-for-me), which adds --force (-f)
option to dropdb utility.
Pros: This seems to be a desired option for many sysadmins, as this
thread proves:
https://dba.stackexchange.com/questions/11893/force-drop-db-while-others-may-be-connected
Cons: another possible foot
