Hi!
> 7 нояб. 2018 г., в 11:48, Evgeniy Efimkin написал(а):
> It would be nice if ALTER USER ... WITH CONNECTION LIMIT will work for
> superuser. It would protect against connection leaks. e.g. we have two
> superusers, one of them reached connection limit but not max_connections, the
> other
On 5 November 2018 at 20:17, Amit Langote wrote:
> On 2018/11/04 19:07, David Rowley wrote:
>> Perhaps a better design would be to instead of having random special
>> partitioned-table-only fields in ResultRelInfo, just have an extra
>> struct there that contains the extra partition information
On Tue, Nov 6, 2018 at 9:16 PM Kyotaro HORIGUCHI
wrote:
>
> Hello. Thank you for the new version.
>
> At Thu, 1 Nov 2018 11:58:52 +0100, Alexander Kukushkin
> wrote in
> > Hi,
> >
> > Attached rebased version patch to the current HEAD and created commit fest
> > entry
> > On Fri, 21 Sep 2018
Hi Alvaro,
Thanks for your help.
Here is the regression.diffs file.
About the root cause, I noticed that, for the 2nd error:
< ERROR: cannot convert infinity to jsonb
< CONTEXT: PL/Perl function "roundtrip"
---
>
(2018/11/07 9:22), Kyotaro HORIGUCHI wrote:
At Tue, 06 Nov 2018 21:07:37 +0900, Etsuro Fujita wrote
in<5be18409.2070...@lab.ntt.co.jp>
(2018/11/06 12:53), Kyotaro HORIGUCHI wrote:
At Fri, 02 Nov 2018 22:05:36 +0900, Etsuro
Fujita wrote
in<5bdc4ba0.7050...@lab.ntt.co.jp>
(2018/10/29 15:58),
Connection limit doesn't work for superuser
Hi hackers!
It would be nice if ALTER USER ... WITH CONNECTION LIMIT will work for
superuser. It would protect against connection leaks. e.g. we have two
superusers, one of them reached connection limit but not max_connections, the
other is still
On 30.10.2018 06:01, Michael Paquier wrote:
On Mon, Oct 29, 2018 at 12:09:21PM +0300, Alexey Kondratov wrote:
Currently in the patch, with dry-run option (-n) pg_rewind only fetches
missing WALs to be able to build file map, while doesn't touch any data
files. So I guess it behaves exactly as
Bonjour Michaël,
First, it seems to me that it is necessary to overcomplicate the
interface of psql for that. Most of the other formats don't have their
own switch, and it is perfectly possible to use CSV format with just
--pset=format=csv.
Although this work, it is not very user friendly
AFAIK, When CREATE INDEX on a partition and INSERT to a parent table are
executed at the same time, this patch causes deadlock.
* partitions information
Partition key: RANGE (a)
Partitions: a_1 FOR VALUES FROM (1) TO (100),
a_2 FOR VALUES FROM (100) TO (200)
T1: create index a_1_ix
On Tue, Nov 06, 2018 at 02:57:15PM +0100, Daniel Verite wrote:
> Here's a rebased version following these changes.
Thanks for doing a rebase.
First, it seems to me that it is necessary to overcomplicate the
interface of psql for that. Most of the other formats don't have their
own switch, and
From: Dmitry Dolgov [mailto:9erthali...@gmail.com]
>Also what's strange for me is that after applying your patches I still got the
>same output, not sure why:
Hmm... In my environment, the output was changed.
I also updated regression test and cfbot.cputube.org reports no problem now.
Do you
101 - 111 of 111 matches
Mail list logo