On Mon, Jun 13, 2016 at 2:42 PM, Tatsuro Yamada
wrote:
> I got mistake to write an e-mail to -hackers on last week. :-<
> I should have written this.
>
> The bug has not fixed by Tom Lane's patch: commit aeb9ae6.
> Because I got the same error using tpc-h.
This looks like a different regressi
On Mon, Jun 13, 2016 at 9:53 AM, Thom Brown wrote:
> On 12 June 2016 at 12:51, Michael Paquier wrote:
>>
>> On Sun, Jun 12, 2016 at 7:52 PM, Thom Brown wrote:
>> > Aren't those already set by recoveryStopsBefore()?
>>
>> It is possible to exit the main redo loop if a NULL record is found
>> afte
Hi,
Subject: Re: [HACKERS] ORDER/GROUP BY expression not found in targetlist
Date: Thu, 09 Jun 2016 12:08:01 +0900
Right, I saw that thread which involved the same error message:
https://www.postgresql.org/message-id/flat/20160526021235.w4nq7k3gnheg7vit%40alap3.anarazel.de#20160526021235.w4nq
On Sat, Jun 11, 2016 at 1:24 AM, Robert Haas wrote:
>
> 3. vacuumlazy.c includes this code:
>
> if (heap_prepare_freeze_tuple(tuple.t_data, FreezeLimit,
> MultiXactCutoff,
&frozen[nfrozen]))
> frozen[nfrozen++].offset =
On 13 June 2016 at 15:39, Thomas Munro wrote:
> What is going on here?
...
>
> postgres=# set max_parallel_workers_per_gather = 2;
> SET
> postgres=# explain select length(data) from logs group by length(data);
> ERROR: ORDER/GROUP BY expression not found in targetlist
Seems like this was caus
On Sun, Jun 12, 2016 at 4:13 PM, Ants Aasma wrote:
>> I feel separate file is better to include the key data instead of pg_control
>> file.
>
> I guess that would be more flexible. However I think at least the fact
> that the database is encrypted should remain in the control file to
> provide use
On Fri, Jun 10, 2016 at 5:23 AM, Haribabu Kommi
wrote:
> 1. Instead of doing the entire database files encryption, how about
> providing user an option to protect only some particular tables that
> wants the encryption at table/tablespace level. This not only provides
> an option to the user, it r
On Mon, Jun 13, 2016 at 4:16 PM, Tatsuro Yamada
wrote:
> I tried to run tpc-h queries, but some queries failed by the error on last
> week.
>
>>Subject: Re: [HACKERS] ORDER/GROUP BY expression not found in targetlist
>>Date: Thu, 09 Jun 2016 12:08:01 +0900
Right, I saw that thread which involved
Hi,
I tried to run tpc-h queries, but some queries failed by the error on last week.
>Subject: Re: [HACKERS] ORDER/GROUP BY expression not found in targetlist
>Date: Thu, 09 Jun 2016 12:08:01 +0900
Today, I try it again by changing max_parallel_workers_per_gather parameter.
The result of Q1 is
Hi,
What is going on here?
postgres=# create table logs as select generate_series(1,
100)::text as data;
SELECT 100
postgres=# insert into logs select * from logs;
INSERT 0 100
postgres=# insert into logs select * from logs;
INSERT 0 200
postgres=# insert into logs select * from l
Robert Haas writes:
> On Tue, Jun 7, 2016 at 10:41 AM, Amit Kapila wrote:
>> I think it will be better if users can have an option to checksum clog
>> pages. However, I think that will need a change in page (CLOG-page) format
>> which might not be a trivial work to accomplish.
> Doesn't the pd_
On Tue, Jun 7, 2016 at 10:41 AM, Amit Kapila wrote:
> I think it will be better if users can have an option to checksum clog
> pages. However, I think that will need a change in page (CLOG-page) format
> which might not be a trivial work to accomplish.
Doesn't the pd_checksum field exist on SLRU
Robert Haas writes:
> On Sun, Jun 12, 2016 at 10:55 AM, Ioseph Kim wrote:
>> Increase size of this title, please.
>> 50 bytes is so small for multi language.
>>
>> And. I suggest that date string might be local language,
>> or current_timestamp string.
> This was already changed in commit dea2b
On Sun, Jun 12, 2016 at 10:55 AM, Ioseph Kim wrote:
> Hello.
> In po.ko (korean message) at psql
> #: command.c:2971
> #, c-format
> msgid "Watch every %lds\t%s"
> msgstr "%ld초 간격으로 지켜보기\t%s"
>
> this message string is a cut string, because buffer size is small.
> At line 2946 in src/bin/psql/comm
On Sat, Jun 11, 2016 at 6:24 PM, Julien Rouhaud
wrote:
> On 11/06/2016 23:37, Julien Rouhaud wrote:
>> On 09/06/2016 16:04, Robert Haas wrote:
>>> OK, I pushed this after re-reviewing it and fixing a number of
>>> oversights. There remains only the task of adding max_parallel_degree
>>> as a syst
On 12 June 2016 at 12:51, Michael Paquier wrote:
> On Sun, Jun 12, 2016 at 7:52 PM, Thom Brown wrote:
> > Aren't those already set by recoveryStopsBefore()?
>
> It is possible to exit the main redo loop if a NULL record is found
> after calling ReadRecord, in which case those would not be set, n
Hi Vladimir,
Thanks for these reports.
On 2016-06-13 00:42:19 +0300, Vladimir Borodin wrote:
> perf report -g -i pg9?_all.data >/tmp/pg9?_perf_report.txt
Any chance you could redo the reports with --no-children --call-graph=fractal
added? The mode that includes child overheads unfortunately make
Hello.
In po.ko (korean message) at psql
#: command.c:2971
#, c-format
msgid "Watch every %lds\t%s"
msgstr "%ld초 간격으로 지켜보기\t%s"
this message string is a cut string, because buffer size is small.
At line 2946 in src/bin/psql/command.c
chartitle[50];
size of message string for korean
On Sun, Jun 12, 2016 at 7:52 PM, Thom Brown wrote:
> Aren't those already set by recoveryStopsBefore()?
It is possible to exit the main redo loop if a NULL record is found
after calling ReadRecord, in which case those would not be set, no?
--
Michael
--
Sent via pgsql-hackers mailing list (pg
On 11 June 2016 at 13:22, Michael Paquier wrote:
> On Sat, Jun 11, 2016 at 9:44 AM, Thom Brown wrote:
> > It may be the wrong way of going about it, but you get the idea of what
> I'm
> > suggesting we output instead.
>
> Surely things could be better. So +1 to be more verbose here.
>
> +
On Sun, Jun 12, 2016 at 12:46 AM, David Steele wrote:
> On 6/11/16 8:22 AM, Michael Paquier wrote:
>> On Sat, Jun 11, 2016 at 9:44 AM, Thom Brown wrote:
>>> It may be the wrong way of going about it, but you get the idea of what I'm
>>> suggesting we output instead.
>>
>> Surely things could be b
On Thu, Jun 09, 2016 at 12:04:59PM -0400, Peter Eisentraut wrote:
> On 6/6/16 9:45 PM, Peter Eisentraut wrote:
> >There appears to be a problem with how client encoding is handled in the
> >communication from parallel workers.
>
> I have added this to the open items for now.
[Action required with
22 matches
Mail list logo
