Re: Error on vacuum: xmin before relfrozenxid

Hi! > 24 мая 2018 г., в 0:55, Paolo Crosato написал(а): > > 1) VACUUM FULL was issued after the first time the error occurred, and a > couple of times later. CLUSTER was never run. > 2) Several failovers tests were perfomed before the cluster was moved to >

Re: PG11 jit failing on ppc64el

On Thu, May 24, 2018 at 3:48 PM, Tom Lane wrote: > Thomas Munro writes: >> BTW It is working on arm64 too, starting with LLVM 6. 5 crashed the >> same way as it does on ppc. See build farm member eelpout which is >> running Debian. > > For

Re: PANIC during crash recovery of a recently promoted standby

On Mon, May 14, 2018 at 01:14:22PM +0530, Pavan Deolasee wrote: > Looks like I didn't understand Alvaro's comment when he mentioned it to me > off-list. But I now see what Michael and Alvaro mean and that indeed seems > like a problem. I was thinking that the test for (ControlFile->state == >

Re: SPI/backend equivalent of extended-query Describe(statement)?

On 05/14/18 13:46, Chapman Flack wrote: > On 05/14/18 11:29, Tom Lane wrote: >> Chapman Flack writes: >>> The longer version of $subject is: how would one go about, in the >>> backend using SPI (or SPI and maybe other server APIs as needed), >>> obtaining the same inferred

Re: Shared PostgreSQL libraries and symbol versioning

On Wednesday, May 23, 2018 2:23:24 PM CEST Pavel Raiskup wrote: > Thanks Stephen, > > On Wednesday, May 23, 2018 1:13:08 PM CEST Stephen Frost wrote: > > Greetings, > > > > * Pavel Raiskup (prais...@redhat.com) wrote: > > > On Thursday, May 10, 2018 12:41:40 PM CEST Pavel Raiskup wrote: > > > >

Re: Shared PostgreSQL libraries and symbol versioning

Re: Pavel Raiskup 2018-05-24 <101829257.nn0xsvv...@nb.usersys.redhat.com> > > Interesting, thanks. How this is implemented? What you mean by "newer > > library" -- new soname, or just a newer package build (without any other > > change) e.g.? > > I've already done some observation how libraries

Re: PG11 jit failing on ppc64el

Thomas Munro writes: > On Thu, May 24, 2018 at 3:48 PM, Tom Lane wrote: >> For entertainment's sake, I tried building --with-llvm on FreeBSD 12 >> arm64 (hey, gotta do something with this raspberry pi toy I got). > Neat. Quite tempted to get

Locks on unlogged tables are locked?!

While looking at this: https://stackoverflow.com/q/50413623/6464308 I realized that "LOCK TABLE " puts a Standby/LOCK into the WAL stream, which causes a log flush at COMMIT time. That hurts performance, and I doubt that it is necessary. At any rate, DROP TABLE on an unlogged table logs nothing.

Function Overloading

Hi Professionals, I hope you are all doing good. Actually I got one problem. I have 2 functions like below. Those are having 11 and 14 parameters with commonly last parameter is variadic array type. func_get_item_list_phy_param(smallint, numeric, numeric, character varying, character

computing z-scores

You construct a z-score for a set of values by subtracting the average from the value and dividing the result by the standard deviation. I know how to do this in a two-step procedure. First, I compute the average and standard deviation. In a second run I use the formula and apply it to each

Unexpected casts while using date_trunc()

I have an application generating the following query on a DATE column in PostgreSQL 10.1: > SELECT TO_CHAR(DATE_TRUNC('month', jobs.active_until), '-MM') > FROM jobs > GROUP BY DATE_TRUNC('month', jobs.active_until) > LIMIT 500 I wanted to support it with an expression index, but was

Re: [HACKERS] Clock with Adaptive Replacement

On Wed, May 2, 2018 at 12:27:19PM -0400, Robert Haas wrote: > I've seen customer have very good luck going higher if it lets all the > data fit in shared_buffers, or at least all the data that is accessed > with any frequency. I think it's useful to imagine a series of > concentric working sets

Re: Should we add GUCs to allow partition pruning to be disabled?

On Wed, May 2, 2018 at 07:49:42PM -0700, David G. Johnston wrote: > On Wednesday, May 2, 2018, Alvaro Herrera wrote: > > Robert Haas wrote: > > On Wed, May 2, 2018 at 9:28 AM, Alvaro Herrera > > wrote: > > > I admit I am more

Portability concerns over pq_sendbyte?

In PG11, pq_sendbyte got changed from taking an int parameter to taking an int8. While that seems to work in general, it does mean that there are now several places in the code that do the equivalent of: unsigned char x = 128; pq_sendbyte(, x); which I believe is not well-defined since

Re: computing z-scores

On Thursday, May 24, 2018, David G. Johnston wrote: > On Thu, May 24, 2018 at 8:15 AM, Martin Mueller < > martinmuel...@northwestern.edu> wrote: > >> You construct a z-score for a set of values by subtracting the average >> from the value and dividing the result by

Re: computing z-scores

On Thu, May 24, 2018 at 8:15 AM, Martin Mueller < martinmuel...@northwestern.edu> wrote: > You construct a z-score for a set of values by subtracting the average > from the value and dividing the result by the standard deviation. I know > how to do this in a two-step procedure. First, I compute

Re: Should we add GUCs to allow partition pruning to be disabled?

On Thu, May 24, 2018 at 02:23:17PM -0400, Alvaro Herrera wrote: > On 2018-May-24, Bruce Momjian wrote: > > > On Wed, May 2, 2018 at 07:49:42PM -0700, David G. Johnston wrote: > > > > I toss my +1 to removing it altogether. > > > > +1 We are terrible at removing old GUCs and having it around

Re: A Japanese-unfriendy error message contruction

Kyotaro HORIGUCHI writes: > Hello. Here is the patch set. Thanks! I pushed all this plus fixes for the OCLASS_PUBLICATION_REL code. The only non-cosmetic change I made was that I didn't much like what you'd done with the OCLASS_DEFACL code: it seemed quite

Re: Should we add GUCs to allow partition pruning to be disabled?

On 2018-May-24, Bruce Momjian wrote: > On Wed, May 2, 2018 at 07:49:42PM -0700, David G. Johnston wrote: > > I toss my +1 to removing it altogether. > > +1 We are terrible at removing old GUCs and having it around means > everyone has to decide if they need to change it, so having it is not a

Re: Unexpected casts while using date_trunc()

> "Tom" == Tom Lane writes: Tom> Yeah. There are two relevant variants of date_trunc(): [...] Tom> So we probably ought to change the docs here. There's also the option of adding an explicit function date_trunc(text,date) returns date, which is a workaround that I

PostgreSQL 11 beta1 : regressions failed on OpenBSD with JIT

Hello, I'm the maintainer of PostgreSQL on OpenBSD. Today I tried the beta1 of PostgreSQL 11 on OpenBSD -current @amd64. Without JIT, everything works fine. When i enable JIT, regress tests fail with this error : indexing ... FAILED (test process exited with exit code 2)

Re: Unexpected casts while using date_trunc()

Chris Bandy writes: > The documentation explains that DATE is first cast to TIMESTAMP. (As I > understand it, this is an immutable cast; sounds find and appropriate.) > https://www.postgresql.org/docs/current/static/functions-datetime.html#FUNCTIONS-DATETIME-TRUNC > But in

Re: Error on vacuum: xmin before relfrozenxid

2018-05-24 8:30 GMT+02:00 Andrey Borodin : > Hi! > > > 24 мая 2018 г., в 0:55, Paolo Crosato > написал(а): > > > > 1) VACUUM FULL was issued after the first time the error occurred, and a > couple of times later. CLUSTER was never run. > > 2)

contrib/sepgsql fails on Fedora 28

I tried to run the regression test for sepgsql on F28 (so I could fix the now-obsolete expected-file therein). It fails at this preparatory step: $ sudo semodule -u sepgsql-regtest.pp The --upgrade option is deprecated. Use --install instead. neverallow check failed at

Keeping temporary tables in shared buffers

Hello We are evaluating the use of shared buffers for temporary tables. The advantage being queries involving temporary tables can make use of parallel workers. Challenges: 1. We lose the performance benefit of local buffers. 2. Additional complexity in shared buffer manager - BufferTag needs

Re: ParseDateTime in src/backend/utils/adt/datetime.c

On Thu, May 3, 2018 at 12:21:45PM +0100, Vladimir Svedov wrote: > Hi guys, > https://stackoverflow.com/questions/50153122/ > how-come-this-postgres-query-is-working > Above guys are surprised by "ignore other punctuation but use as delimiter" > part. > Do you think this should be mentioned in

add default parallel query to v10 release notes? (Re: [PERFORM] performance drop after upgrade (9.6 > 10))

Moving to -hackers; On Sun, Jan 28, 2018 at 06:53:10PM -0500, Bruce Momjian wrote: > On Thu, Oct 26, 2017 at 02:45:15PM -0500, Justin Pryzby wrote: > > Is it because max_parallel_workers_per_gather now defaults to 2 ? > > > > BTW, I would tentatively expect a change in default to be documented

Re: A Japanese-unfriendy error message contruction

At Thu, 24 May 2018 14:20:21 -0400, Tom Lane wrote in <24988.1527186...@sss.pgh.pa.us> > Kyotaro HORIGUCHI writes: > > Hello. Here is the patch set. > > Thanks! I pushed all this plus fixes for the OCLASS_PUBLICATION_REL > code. Thanks. >

Re: [GSoC] github repo and initial work

Hi guys, As mentioned in the last email that the current interface is based on bytea. To make users easily insert any thrift data structure and show them, we may want to have user friendly (user readable) format for this plugin. I can think about 2 ways to do this. One is to provide

Re: A Japanese-unfriendy error message contruction

Hello. Here is the patch set. At Wed, 23 May 2018 11:20:24 -0400, Tom Lane wrote in <4979.1527088...@sss.pgh.pa.us> > After thinking about this some more, I'd like to propose that we change > the English output to be "column COLNAME of ", using code > similar to what you

Re: Function Overloading

ramsiddu007 writes: > I hope you are all doing good. Actually I got one problem. I > have 2 functions like below. Those are having 11 and 14 parameters with > commonly last parameter is variadic array type. > func_get_item_list_phy_param(smallint, numeric,

Re: [PATCH v15] GSSAPI encryption support

Thomas Munro writes: > On Thu, May 24, 2018 at 8:00 AM, Robbie Harwood wrote: > >> Zombie patch is back from the dead. > > Hi Robbie, > > Robots[1] vs zombies: > > + $postgres->RemoveFile('src/backennd/libpq/be-gssapi-common.c'); > > Typo,

Re: Portability concerns over pq_sendbyte?

On Thu, May 24, 2018 at 06:13:23PM +0100, Andrew Gierth wrote: > In PG11, pq_sendbyte got changed from taking an int parameter to taking > an int8. From 1de09ad8. > While that seems to work in general, it does mean that there are now > several places in the code that do the equivalent of: > >

Add PostgreSQL 11 to feature matrix page?

Now that PostgreSQL 11 beta is out, I wonder if it's worth to add PostgreSQL 11 to the feature matrix page. https://www.postgresql.org/about/featurematrix/ Adding PostgreSQL 11 to the page will give users at-a-glance-dfference between 11 and previous releases, which could bring clearner image of

Re: Add PostgreSQL 11 to feature matrix page?

> On May 24, 2018, at 9:38 PM, Tatsuo Ishii wrote: > > Now that PostgreSQL 11 beta is out, I wonder if it's worth to add > PostgreSQL 11 to the feature matrix page. > > https://www.postgresql.org/about/featurematrix/ > > Adding PostgreSQL 11 to the page will give users

Re: Keeping temporary tables in shared buffers

Asim Praveen writes: > We are evaluating the use of shared buffers for temporary tables. The > advantage being queries involving temporary tables can make use of parallel > workers. Hm... > Challenges: > 1. We lose the performance benefit of local buffers. Yeah. This

Redesigning the executor (async, JIT, memory efficiency)

Hi, The current executor structure limits us in a number of ways that are becoming problematic. I'll outline in this email how I think we should rework it. Including a prototype for the first, most drastic, steps. The primary problems with the current design that I want to address are: 1)

Re: Fix some error handling for read() and errno

At Wed, 23 May 2018 09:00:40 +0900, Michael Paquier wrote in <2018052340.ga3...@paquier.xyz> > On Tue, May 22, 2018 at 04:51:00PM +0900, Kyotaro HORIGUCHI wrote: > > I see the same issue in snapbuild.c(4 places). > > > > | readBytes = read(fd, ,

Re: Compiler warnings with --enable-dtrace

On Wed, May 23, 2018 at 5:17 AM, Christoph Berg wrote: > I'm not aware of any guidelines - I guess this stuff is still too new > to make general statements about it. Which other software offers > custom probes? As the LWN article mentions, user space probes are available for a

Re: contrib/sepgsql fails on Fedora 28

On 05/24/2018 03:30 PM, Tom Lane wrote: > I tried to run the regression test for sepgsql on F28 (so I could > fix the now-obsolete expected-file therein). It fails at this > preparatory step: > > $ sudo semodule -u sepgsql-regtest.pp > The --upgrade option is deprecated. Use --install instead. >

Re: Shared PostgreSQL libraries and ABI versioning

Hi Christoph, On Thursday, May 24, 2018 12:08:16 PM CEST Christoph Berg wrote: > Re: Pavel Raiskup 2018-05-24 <101829257.nn0xsvv...@nb.usersys.redhat.com> > > > Interesting, thanks. How this is implemented? What you mean by "newer > > > library" -- new soname, or just a newer package build

XLogWrite uses palloc within a critical section

Hello. I happened to see the following in XLogWrite. > ereport(PANIC, > (errcode_for_file_access(), > errmsg("could not seek in log file %s to offset %u: %m", > XLogFileNameP(ThisTimeLineID, openLogSegNo), > startoffset))); where XLogFileNameP calls palloc within,

In what range of the code can we read debug_query_string?

Hello. While looking into *some* tool that heavily reliant on debug_query_string, I found that the tool can miss it. However I believed that it is always set when post_parse_analyze_hook is called, it is not while processing DESCRIBE message of extended protocol. I believe that the assumption is

pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced

Hi all, When attempting to use multiple times pg_replication_slot_advance on a slot, then the caller gets back directly InvalidXLogRecPtr as result, for example: =# select * from pg_replication_slot_advance('popo', 'FF/0'); slot_name | end_lsn ---+--- popo | 0/60021E0 (1