On 09.02.2018 10:47, Sergei Kornilov wrote:
Hello
select into b from my_insert('from func atx');
You missed select something into b. For example,
select ret into b from my_insert('from func atx') as ret;
Using scalar function in from is not bug.
Silent assigning NULL for variables in "into"
Hello.
I happend to find that server crashes during regtest when
DSM_NONE is enforced. The attached patch fixes that.
The cause is the fact that _bt_spools_heapscan runs
_bt_begin_parallel() even if dynamic_shared_memory_type is
DSM_NONE. It is because plan_create_index_workers() is ignoring
dyna
Hello.
I'm not sure such a case happens in the real world nowadays,
initdb uses the fallback value of max_connections=10. But it is
out of favor of server since it is not larger than
max_wal_senders(10).
> postgres: max_wal_senders must be less than max_connections
I think that we can safely inc
Hello.
At Thu, 08 Feb 2018 18:21:56 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
wrote in
<20180208.182156.96551245.horiguchi.kyot...@lab.ntt.co.jp>
> I suppose that the problem has not been resolved yet..
I found several bugs during studying this but my conclusion here
is that the required
On Tue, Feb 6, 2018 at 10:07 AM, Stephen Frost wrote:
>
> That was also what seemed to be the consensus coming out of the FOSDEM
> Developer meeting (notes here:
> https://wiki.postgresql.org/wiki/FOSDEM/PGDay_2018_Developer_Meeting).
>
>
In the notes there is this, which confused me:
> SIDE TO
On 09.02.2018 11:02, Konstantin Knizhnik wrote:
On 09.02.2018 10:47, Sergei Kornilov wrote:
Hello
select into b from my_insert('from func atx');
You missed select something into b. For example,
select ret into b from my_insert('from func atx') as ret;
Using scalar function in from is not
On 09.02.2018 11:58, Konstantin Knizhnik wrote:
On 09.02.2018 11:02, Konstantin Knizhnik wrote:
On 09.02.2018 10:47, Sergei Kornilov wrote:
Hello
select into b from my_insert('from func atx');
You missed select something into b. For example,
select ret into b from my_insert('from func
On Fri, Feb 9, 2018 at 8:55 AM, Pantelis Theodosiou
wrote:
> On Tue, Feb 6, 2018 at 10:07 AM, Stephen Frost wrote:
>
>>
>> That was also what seemed to be the consensus coming out of the FOSDEM
>> Developer meeting (notes here:
>> https://wiki.postgresql.org/wiki/FOSDEM/PGDay_2018_Developer_Meet
On Fri, Feb 09, 2018 at 08:55:26AM +, Pantelis Theodosiou wrote:
> On Tue, Feb 6, 2018 at 10:07 AM, Stephen Frost wrote:
>> SIDE TOPIC:
>>
>> Release date for PostgreSQL 13 agreed: Friday 13th September 2019!!
>
> Isn't Postgres 12 to be released in 2019? And 13 in 2020?
Translate that with
(2018/02/09 10:48), Etsuro Fujita wrote:
(2018/02/09 4:32), Robert Haas wrote:
On Thu, Feb 8, 2018 at 11:05 AM, Tom Lane wrote:
there's still an intermittent issue. I ran "make installcheck" in
contrib/postgres_fdw in a loop, and got a similar failure on the
47th try --- my result duplicates th
(2018/02/08 23:21), Robert Haas wrote:
On Thu, Feb 8, 2018 at 5:16 AM, Etsuro Fujita
wrote:
if (resultRelInfo == NULL);
{
/* Initialize partition info. */
resultRelInfo = ExecInitPartitionInfo(mtstate,
saved_resultRelIn
On Fri, Feb 9, 2018 at 9:58 AM, Konstantin Knizhnik <
k.knizh...@postgrespro.ru> wrote:
> Attached please find patch reporting error in case of empty attribute list
> for SELECT INTO
>
This is quite short-sighted. The better way to do this is to complain if
the number of expressions is different
Hi
2018-02-09 7:56 GMT+01:00 Michael Paquier :
> On Fri, Feb 02, 2018 at 04:07:28PM +0900, Michael Paquier wrote:
> > You need to read that as "only a SubPlan can be executed after a SubLink
> > has been processed by the planner", so please replace the last "latter"
> > by "planner".
>
> (I forgo
2018-02-09 12:02 GMT+01:00 Marko Tiikkaja :
> On Fri, Feb 9, 2018 at 9:58 AM, Konstantin Knizhnik <
> k.knizh...@postgrespro.ru> wrote:
>
>> Attached please find patch reporting error in case of empty attribute
>> list for SELECT INTO
>>
>
> This is quite short-sighted. The better way to do this
On 08.02.2018 21:01, Andres Freund wrote:
On 2018-02-08 14:48:34 -0300, Alvaro Herrera wrote:
Ildar Musin wrote:
The idea is to store min and max values of secondary attributes
(like 'id' in the example above) for each partition somewhere in
catalog and use it for partition pruning along wit
(2018/02/09 14:32), Amit Langote wrote:
I had mistakenly tagged these patches v24, but they were actually supposed
to be v5. So the attached updated patch is tagged v6.
OK.
On 2018/02/07 19:36, Etsuro Fujita wrote:
(2018/02/05 14:34), Amit Langote wrote:
The code in tupconv_map_for_subplan
On Thu, Feb 8, 2018 at 8:39 PM, Alvaro Herrera wrote:
> Claudio Freire wrote:
>
>> I don't like looping, though, seems overly cumbersome. What's worse?
>> maintaining that fragile weird loop that might break (by causing
>> unexpected output), or a slight slowdown of the test suite?
>>
>> I don't k
Hi,
Name for wait event "LWTRANCHE_OLDSERXID_BUFFERS" is printed as
"oldserxid", but documentation at
https://www.postgresql.org/docs/10/static/monitoring-stats.html does
not have exact same event there. Instead it has
OldSerXidLock Waiting to read or record conflicting serializable
transactio
Ildar Musin wrote:
> But if we filter the table by 'id' then planner has no other way but to
> append every partition to the plan.
>
> EXPLAIN (COSTS OFF) SELECT * FROM events WHERE id = 123;
> Append
>-> Seq Scan on events_0
> Filter: (id = 123)
>-> Seq Scan on events_1
>
On Thu, Feb 8, 2018 at 7:49 PM, Robert Haas wrote:
> On Thu, Feb 8, 2018 at 9:04 AM, Amit Kapila wrote:
>>> Also, if you're OK with not being able to do anything except fetch
>>> from the cursor until you reach the end, then couldn't you just issue
>>> the query without the cursor and use PQsetSi
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Fri, Feb 09, 2018 at 08:55:26AM +, Pantelis Theodosiou wrote:
> > On Tue, Feb 6, 2018 at 10:07 AM, Stephen Frost wrote:
> >> SIDE TOPIC:
> >>
> >> Release date for PostgreSQL 13 agreed: Friday 13th September 2019!!
> >
> > Isn't Postgres 12
Hi Stas,
> Reading through patch I’ve noticed that you deleted call to
> SnapBuildCommitTxn()
> in DecodePrepare(). As you correctly spotted upthread there was unnecessary
> code that marked transaction as running after decoding of prepare. However
> call
> marking it as committed before decodi
On Fri, Feb 09, 2018 at 12:02:57PM +0100, Pavel Stehule wrote:
> 2018-02-09 7:56 GMT+01:00 Michael Paquier :
> > The second problem involves a cache lookup failure for a type when
> > trying to use pg_get_functiondef on a procedure. Luckily, it is
> > possible to make the difference between a proc
On Fri, Feb 09, 2018 at 07:55:32AM -0500, Stephen Frost wrote:
> * Michael Paquier (mich...@paquier.xyz) wrote:
> > Translate that with "Friday 13th as a lucky or unlucky date for Postgres
> > 13". And also translate it to a joke.
>
> Indeed. Besides, the real date will be 2020-11-13. ;)
This m
Claudio Freire wrote:
> On Thu, Feb 8, 2018 at 8:39 PM, Alvaro Herrera
> wrote:
> During the process of developing the patch, I got seriously broken
> code that passed the tests nonetheless. The test as it was was very
> ineffective at actually detecting issues.
>
> This new test may be slow, b
On Fri, Feb 09, 2018 at 06:04:39PM +0530, Ashutosh Bapat wrote:
> Name for wait event "LWTRANCHE_OLDSERXID_BUFFERS" is printed as
> "oldserxid", but documentation at
> https://www.postgresql.org/docs/10/static/monitoring-stats.html does
> not have exact same event there. Instead it has
>
> OldSerX
On 02/09/2018 02:27 PM, Michael Paquier wrote:
> On Fri, Feb 09, 2018 at 07:55:32AM -0500, Stephen Frost wrote:
>> * Michael Paquier (mich...@paquier.xyz) wrote:
>>> Translate that with "Friday 13th as a lucky or unlucky date for Postgres
>>> 13". And also translate it to a joke.
>>
>> Indeed.
On Fri, Feb 9, 2018 at 12:56 AM, Garym wrote:
> Hi,
> This is an odd request for help. I'm looking to expose an interface so an
> external app can insert to a table while maintaining cache consistency and
> inserts be promoted via wal.
>
I don't understand what that all means (what cache? inser
On Fri, Feb 9, 2018 at 7:23 PM, Michael Paquier wrote:
> On Fri, Feb 09, 2018 at 06:04:39PM +0530, Ashutosh Bapat wrote:
>> Name for wait event "LWTRANCHE_OLDSERXID_BUFFERS" is printed as
>> "oldserxid", but documentation at
>> https://www.postgresql.org/docs/10/static/monitoring-stats.html does
>
On Fri, Feb 9, 2018 at 6:23 AM, Michael Paquier wrote:
> On Fri, Feb 09, 2018 at 12:02:57PM +0100, Pavel Stehule wrote:
> > 2018-02-09 7:56 GMT+01:00 Michael Paquier :
> > > The second problem involves a cache lookup failure for a type when
> > > trying to use pg_get_functiondef on a procedure.
2018-02-09 15:15 GMT+01:00 David G. Johnston :
> On Fri, Feb 9, 2018 at 6:23 AM, Michael Paquier
> wrote:
>
>> On Fri, Feb 09, 2018 at 12:02:57PM +0100, Pavel Stehule wrote:
>> > 2018-02-09 7:56 GMT+01:00 Michael Paquier :
>> > > The second problem involves a cache lookup failure for a type when
On Thu, Feb 8, 2018 at 8:23 PM, Peter Geoghegan wrote:
> Some novel new behavior -- "EPQ with a twist"-- is clearly necessary.
> I feel a bit uneasy about it because anything that anybody suggests is
> likely to be at least a bit arbitrary (EPQ itself is kind of
> arbitrary). We only get to make a
On 9 February 2018 at 15:56, Garym wrote:
> Hi,
> This is an odd request for help. I'm looking to expose an interface so an
> external app can insert to a table while maintaining cache consistency and
> inserts be promoted via wal.
>
> I need to support about 100k+ inserts/sec from a sensor data
"David G. Johnston" writes:
> On Fri, Feb 9, 2018 at 6:23 AM, Michael Paquier wrote:
>> On Fri, Feb 09, 2018 at 12:02:57PM +0100, Pavel Stehule wrote:
>>> Blocking subqueries in CALL parameters is possible solution.
> To me this feels like an interaction between two features that users are
> goi
On Fri, Feb 9, 2018 at 7:42 AM, Tom Lane wrote:
> "David G. Johnston" writes:
> > On Fri, Feb 9, 2018 at 6:23 AM, Michael Paquier
> wrote:
> >> On Fri, Feb 09, 2018 at 12:02:57PM +0100, Pavel Stehule wrote:
> >>> Blocking subqueries in CALL parameters is possible solution.
>
> > To me this feel
On Fri, Feb 9, 2018 at 1:36 AM, Masahiko Sawada wrote:
> On Fri, Feb 9, 2018 at 12:45 AM, Claudio Freire
> wrote:
>> On Thu, Feb 8, 2018 at 1:36 AM, Masahiko Sawada
>> wrote:
>>> On Tue, Feb 6, 2018 at 9:51 PM, Claudio Freire
>>> wrote:
I can look into doing 3, that *might* get rid of t
On Thu, Feb 1, 2018 at 8:16 PM, Thomas Munro
wrote:
> On Fri, Feb 2, 2018 at 2:05 PM, Andres Freund wrote:
>> On 2018-02-01 09:32:17 -0800, Jeff Davis wrote:
>>> On Wed, Jan 31, 2018 at 12:03 AM, Konstantin Knizhnik
>>> wrote:
>>> > The same problem takes place with old versions of GCC: I have t
Attached please find new version of built-in connection pooling
supporting temporary tables and session GUCs.
Also Win32 support was added.
--
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
diff --git a/src/backend/catalog/namespace.c b/src/b
> On 7 February 2018 at 22:51, Dmitry Dolgov <9erthali...@gmail.com> wrote:
>> On 6 February 2018 at 10:17, Arthur Zakirov wrote:
>> It is strange. I still can apply both v9 [1] and v10 [2] via 'git
>> apply'. And Patch Tester [3] says that it is applied. But maybe
>> it is because of my git (git
On Fri, Feb 9, 2018 at 10:32 AM, Alvaro Herrera wrote:
> Claudio Freire wrote:
>> On Thu, Feb 8, 2018 at 8:39 PM, Alvaro Herrera
>> wrote:
>
>> During the process of developing the patch, I got seriously broken
>> code that passed the tests nonetheless. The test as it was was very
>> ineffective
On 2018-02-09 09:42:41 -0500, Tom Lane wrote:
> It doesn't look significantly different to me than the restriction
> that you can't have sub-selects in CHECK expressions, index
> expressions, etc. Obviously we need a clean failure like you get for
> those cases. But otherwise it's an OK restricti
On Fri, Feb 9, 2018 at 5:24 AM, Etsuro Fujita
wrote:
> I tried to reproduce that in my environment, but I couldn't. On reflection
> I think an easy and reliable way to address that concern is to use local
> stats on foreign tables. Attached is a patch for that.
Me neither. I just ran the postg
Robert Haas writes:
> Me neither. I just ran the postgres_fdw regression tests 713 times in
> a row without a failure. Tom, since you seem to be able to reproduce
> the problem locally, could you have a look at this proposed fix?
I'm a bit busy, but AFAICS it's just a timing thing, so try inser
On 2018-02-09 09:10:25 -0600, Merlin Moncure wrote:
> Question: when watching the compilation log, I see quite a few files
> being compiled with both O2 and O1, for example:
>
> clang -Wall -Wmissing-prototypes -Wpointer-arith
> -Wdeclaration-after-statement -Wendif-labels
> -Wmissing-format-attr
On Thu, Feb 8, 2018 at 3:58 AM, Masahiko Sawada wrote:
>> Overall, what's the status of this patch? Are we hung up on this
>> issue only, or are there other things?
>
> AFAIK there is no more technical issue in this patch so far other than
> this issue. The patch has tests and docs, and includes
> On 8 February 2018 at 21:26, Thomas Munro
> wrote:
> On Fri, Feb 9, 2018 at 3:14 AM, Dmitry Dolgov <9erthali...@gmail.com> wrote:
>> $ ./configure --prefix=/build/postgres-jit/ --with-llvm
>> --enable-debug --enable-depend --enable-cassert
>
>> /usr/include/c++/5/bits/c++0x_warning.h:32
On Fri, Feb 9, 2018 at 1:33 PM, Tom Lane wrote:
> Robert Haas writes:
>> Me neither. I just ran the postgres_fdw regression tests 713 times in
>> a row without a failure. Tom, since you seem to be able to reproduce
>> the problem locally, could you have a look at this proposed fix?
>
> I'm a bi
On Fri, Feb 9, 2018 at 7:53 AM, Amit Kapila wrote:
> I am not saying to allow other things. I am just replying to your
> question that why can't we use PQsetSingleRowMode. I mean to say that
> one can fetch the data parallelly via the usage of cursors (by having
> restrictions like don't allow o
On Wed, Feb 7, 2018 at 7:04 PM, Thomas Munro
wrote:
> On Tue, Feb 6, 2018 at 5:21 PM, Peter Eisentraut
> wrote:
>> On 9/18/17 22:41, Andres Freund wrote:
>>> Rearm statement_timeout after each executed query.
>>
>> This appears to have broken statement_timeout behavior in master such
>> that only
Hi,
Were you ever able to solve this issue? I am encountering exactly the same
problem on Ubuntu 16.04.
Thank you,
Mikel.
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
On Wed, Feb 7, 2018 at 6:32 AM, Metin Doslu wrote:
> i. The list of Pascal (max_worker_processes was already with
> PGDLLIMPORT, so I also added to max_parallel_workers)
> ii. Some others in cost.h to make the file more readable.
Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.c
Hi,
First off: This patch has way too many different types of changes as
part of one huge commit. This needs to be split into several
pieces. First the cleanups (e.g. the fields -> flag changes), then the
individual infrastructure pieces (like the twophase.c changes, best
split into several pieces
Nikolay Shaplov wrote:
> I found out, that all relation options of string type in current postgres,
> are
> actually behaving as "enum" type.
If this patch gets in, I wonder if there are any external modules that
use actual strings. An hypothetical example would be something like a
SSL cipher
Am a bit late to this thread, sorry if I'm slightly rehashing things. I'd
like to go back to the basic on this.
Unless I'm mistaken, at least in the Java and .NET world, clients are
almost always expected to have their own connection pooling, either
implemented inside the driver (ADO.NET model) or
On Fri, Feb 9, 2018 at 4:14 PM, Shay Rojansky wrote:
> Am a bit late to this thread, sorry if I'm slightly rehashing things. I'd
> like to go back to the basic on this.
>
> Unless I'm mistaken, at least in the Java and .NET world, clients are
> almost always expected to have their own connection
On Thu, Feb 08, 2018 at 09:28:10AM -0500, Tom Lane wrote:
> Michael Paquier writes:
> That seems like possibly not such a great idea. If somebody were using
> a run of src/test/ssl to check their build, they would now get no
> notification if they'd forgotten to build --with-openssl.
>
> Perhaps
On Fri, Feb 09, 2018 at 07:33:57PM +0530, Ashutosh Bapat wrote:
> I didn't pay attention to the second one. Thanks for pointing that
> out. But then like me a user may first land on OldSerXidLock since
> that is first in the list and get confused. May be we should use names
> which are not prefix o
Since commit aaf15e5, a text value doesn't reliably roundtrip through
representation as an XML attribute. At least, not like this:
WITH t(v) AS (SELECT text 'This & That'),
x(e) AS (SELECT xmlelement(name foo, xmlattributes(v)) FROM t),
y(v1) AS (SELECT (xpath('/foo/@v', e))[1]::text FROM x)
SELEC
On 2/8/18 22:56, Thomas Munro wrote:
> The test doesn't actually succeed in reloading the pg_hba.conf
> file though:
>
> 2018-02-09 16:41:15.886 NZDT [24472] LOG: received SIGHUP, reloading
> configuration files
> 2018-02-09 16:41:15.893 NZDT [24472] LOG: unsupported LDAP URL scheme: ldapi
> 201
Hi,
On 02/07/2018 10:24 AM, Pavan Deolasee wrote:
>
> ...
>
> Here is v15 of the patch.
>
I've been looking at this version of the patch, mostly to educate myself
before attempting to write the "status summary".
One bit that I don't quite understand is GetXactWALBytes(). It pretty
much just ret
On Sat, Feb 10, 2018 at 1:07 PM, Michael Paquier wrote:
> On Thu, Feb 08, 2018 at 09:28:10AM -0500, Tom Lane wrote:
>> Michael Paquier writes:
>> That seems like possibly not such a great idea. If somebody were using
>> a run of src/test/ssl to check their build, they would now get no
>> notific
On Sat, Feb 10, 2018 at 4:32 PM, Thomas Munro
wrote:
> I agree that it would be nice if the build farm (and my unofficial
> patch tester for that matter) could automatically test the LDAP stuff
> when running on a suitable system, but I think it would need to be
> based not just on ifeq ($(with_ld
Thanks for the replies.
@Craig
Realtime ? well not really. I guess it's your definition of realtime.. I
usually think of micro to nano seconds as real-time. If I were still
designing chips, I'd be calling picosecs real-time these days.
Thank you for the recommendation on performance tuning tools
63 matches
Mail list logo
