Hi hackers,
Hot experts help is highly needed:)
One of our customers is faced with the following problem:
Session 1:
create table x (i int);
begin;
insert into x values(1);
...
Session 2:
select i as id, 0 as v into t from generate_series(1, 10) i;
create unique index idx on t (id);
explai
On Tue, Jul 03, 2018 at 03:49:44PM +0900, Amit Langote wrote:
> I forgot that expand_partitioned_rtentry() will recursively call itself if
> a partition is itself a partitioned table, in which case the above
> code helps.
Actually look at the coverage reports:
https://coverage.postgresql.org/src/b
Hi,
As I've previously mentioned I had planned to spend some time to polish
Haribabu's version of the pluggable storage patch and rebase it on the
vtable based slot approach from [1]. While doing so I found more and
more things that I previously hadn't noticed. I started rewriting things
into some
On 02.07.18 15:26, Tom Lane wrote:
> FWIW, I agree with Andres' thought that each contrib module should have
> its own subdirectory under $(includedir_server). Otherwise we're going
> to be faced with questions about whether .h files need to be renamed
> because they're not globally unique enough.
On Tue, Jul 3, 2018 at 1:01 PM, Michael Paquier wrote:
> On Mon, Jul 02, 2018 at 04:31:32PM +0900, Masahiko Sawada wrote:
>> Attached an updated patch including copy function support for logical
>> slots as well as physical slots. Please review it.
>
> I had a look at this patch.
Thank you for th
>
>
> > pg_dump --where "bar:created_at >= 2018-05-01'"
>
> I am wondering how this works at parsing if the table name, or one of
> the columns includes a colon character :)
>
The proposed patch will handle quoted identifiers. E.g. the following will
work just fine:
pg_dump --where 'table:"c
On 2018/07/03 17:31, Amit Langote wrote:
> On 2018/07/03 16:05, Michael Paquier wrote:
>> On Tue, Jul 03, 2018 at 03:49:44PM +0900, Amit Langote wrote:
>>> I forgot that expand_partitioned_rtentry() will recursively call itself if
>>> a partition is itself a partitioned table, in which case the abo
On 28 June 2018 at 10:51, Masahiko Sawada wrote:
> Hi,
>
> I'd like to propose a copy function for logical replication slots.
> Currently when we create a new logical replication slot it starts to
> read WAL from an LSN of the current insert. This function copies a
> existing logical replication
Hello. Thanks for the comment.
At Mon, 2 Jul 2018 14:25:58 -0400, Robert Haas wrote in
> On Fri, Jun 29, 2018 at 4:34 AM, Kyotaro HORIGUCHI
> wrote:
> > Nowadays PostgreSQL has dynamic shared hash (dshash) so we can
> > use this as the main storage of statistics. We can share data
> > without
Hi
I Would like to know how to encrypt data with physical public
key files. I can't find any documentation about this subject.
Thanks in advance
Best Regards
[cid:image002.png@01D14E0E.8515EB90]
Didier ROS
Expertise SGBD
DS IT/IT DMA/Solutions Groupe EDF/Expertise
On Tue, Jul 3, 2018 at 6:19 AM, Daniel Gustafsson wrote:
>> On 2 Jul 2018, at 14:01, Masahiko Sawada wrote:
>
>> Thank you for updating the patch! There are two review comments.
>
> Thanks for reviewing!
>
>> The current select_active_windows() function compares the all fields
>> of WindowClause
Following issues are solved:
\dAf[+] [AMPTRN [OPFPTRN]] list operator families of access method.
+
prints owner of operator family. (Table pg_opfamily)
\dAfp[AMPTRN [OPFPTRN]] list procedures of operator family
related
to access method (Table pg_amproc)
* Reorder "Left"/"Right" an
On Tue, Jul 3, 2018 at 7:16 AM, Nico Williams wrote:
> On Mon, Jul 02, 2018 at 06:22:46PM +0900, Masahiko Sawada wrote:
>> On Fri, Jun 22, 2018 at 2:31 PM, Tsunakawa, Takayuki
>> wrote:
>> > From: Nico Williams [mailto:n...@cryptonector.com]
>> >
>> >> One shortcoming of relying on OS functionali
On Mon, Jul 2, 2018 at 9:27 PM, Robert Haas wrote:
>
> But you can specify multiple tables. You wouldn't want the same WHERE
> clause to apply to all of them.
>
> also with this new --where option you can specify multiple table using
wildcard and it
try to apply the same where clause to each tab
On Mon, Jul 2, 2018 at 6:02 PM, Robert Haas wrote:
>
> I think the core problem here is this hunk from gather_readnext:
>
> {
> Assert(!tup);
> -DestroyTupleQueueReader(reader);
> --gatherstate->nreaders;
> if (gatherstate->nreaders == 0)
On Fri, Jun 29, 2018 at 5:26 PM Peter Eisentraut
wrote:
>
> On 6/29/18 13:07, amul sul wrote:
> > This happens because of in fmgr_security_definer() function we are
> > changing global variable SecurityRestrictionContext and in the
> > StartTransaction() insisting it should be zero, which is the
Dear Antonin Houska.
> -Original Message-
> From: Antonin Houska [mailto:a...@cybertec.at]
> Sent: Tuesday, May 29, 2018 3:23 PM
> To: Moon, Insung
> Cc: pgsql-hack...@postgresql.org
> Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key
> Management Service (KMS)
Dear Aleksander Alekseev.
> -Original Message-
> From: Aleksander Alekseev [mailto:a.aleks...@postgrespro.ru]
> Sent: Thursday, May 31, 2018 10:33 PM
> To: Moon, Insung
> Cc: pgsql-hack...@postgresql.org
> Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key
> Man
Dear Masahiko Sawada.
> -Original Message-
> From: Masahiko Sawada [mailto:sawada.m...@gmail.com]
> Sent: Monday, June 11, 2018 6:22 PM
> To: Moon, Insung
> Cc: PostgreSQL-development; Joe Conway
> Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key
> Management
Dear Tomas Vondra.
> -Original Message-
> From: Tomas Vondra [mailto:tomas.von...@2ndquadrant.com]
> Sent: Wednesday, June 13, 2018 10:15 PM
> To: Moon, Insung; pgsql-hack...@postgresql.org
> Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key
> Management Servic
On Tue, Jul 3, 2018 at 6:48 AM, Amit Kapila wrote:
> Yeah, previously, I have also pointed out the same code [1]. However,
> I have not done any testing to prove it.
Ah, OK. Sorry, forgot about that email.
> Are you planning to work on it? If not, then I can look into it.
I won't have time f
Dear Tomas Vondra.
> -Original Message-
> From: Tomas Vondra [mailto:tomas.von...@2ndquadrant.com]
> Sent: Wednesday, June 13, 2018 10:03 PM
> To: Masahiko Sawada; Moon, Insung
> Cc: PostgreSQL-development; Joe Conway
> Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE)
On Tue, Jul 03, 2018 at 07:28:42PM +0900, Masahiko Sawada wrote:
> On Tue, Jul 3, 2018 at 7:16 AM, Nico Williams wrote:
> > Yes, but piecemeal encryption seems like a bad idea to me.
>
> What do you mean by "piecemeal encryption"? Is it not-whole database
> encryption such as per-table or per-tab
Dear Takayuki Tsunakawa.
> -Original Message-
> From: Tsunakawa, Takayuki [mailto:tsunakawa.ta...@jp.fujitsu.com]
> Sent: Thursday, June 14, 2018 9:58 AM
> To: 'Tomas Vondra'; Moon, Insung; pgsql-hack...@postgresql.org
> Subject: RE: [Proposal] Table-level Transparent Data Encryption (TDE)
On Tue, Jul 3, 2018 at 6:31 AM, Surafel Temesgen wrote:
> On Mon, Jul 2, 2018 at 9:27 PM, Robert Haas wrote:
>> But you can specify multiple tables. You wouldn't want the same WHERE
>> clause to apply to all of them.
>>
> also with this new --where option you can specify multiple table using
> w
On 03.07.2018 00:40, Peter Geoghegan wrote:
On Mon, Jul 2, 2018 at 9:28 AM, Peter Geoghegan wrote:
Execution time of last "VACUUM test;" command on my notebook was:
with bulk deletion: 1.6 s;
with Quick Vacuum Strategy: 5.2 s;
with Quick Vacuum Strategy & TID sorting: 0.6 s.
I'm glad that
Dear Joe.
> -Original Message-
> From: Joe Conway [mailto:m...@joeconway.com]
> Sent: Monday, June 18, 2018 9:30 PM
> To: Masahiko Sawada
> Cc: Moon, Insung; PostgreSQL-development
> Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key
> Management Service (KMS)
>
Dear Tom Lane.
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Monday, June 18, 2018 11:52 PM
> To: Robert Haas
> Cc: Joe Conway; Masahiko Sawada; Moon, Insung; PostgreSQL-development
> Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key
On Mon, Jun 25, 2018 at 1:29 AM, Fabien COELHO wrote:
>
> I do not mind spending some time for elegance, but I mind spending time for
> nothing.
>
> I hope some committers will also express their views about the feature.
>
There's a commitfest entry for this but no patch. So I am marking this
as
2018-07-03 14:30 GMT+02:00 Nikita Glukhov :
> Attached 16th version of the patches:
> * changed type of new SQL keyword STRING
>(STRING is used as a function parameter name in Pl/Tcl tests)
> * removed implicit coercion via I/O from JSON_VALUE (see below)
>
>
> On 28.06.2018 07:25, Pavel Ste
On 03/20/2018 01:35 PM, Tomas Vondra wrote:
On 03/20/2018 05:36 AM, Pavel Stehule wrote:
2018-03-19 21:47 GMT+01:00 Tomas Vondra mailto:tomas.von...@2ndquadrant.com>>:
Hi,
I'm looking at the updated patch (plpgsql-extra-check-180316.patch), and
this time it applies and build
On 2018-06-13 16:35:58 +0900, Amit Langote wrote:
> Hi.
>
> On 2018/06/13 14:55, Michael Paquier wrote:
> > On Wed, Jun 13, 2018 at 11:08:38AM +0530, Rajkumar Raghuwanshi wrote:
> >> postgres=# SELECT dense_rank(b) WITHIN GROUP (ORDER BY a) FROM pagg_tab
> >> GROUP BY b ORDER BY 1;
> >> server clo
Hi Ashutosh, Etsuro, Robert,
On 2018-06-22 10:58:28 -0400, Robert Haas wrote:
> On Tue, Jun 19, 2018 at 8:46 AM, Etsuro Fujita
> wrote:
> > Here is a patch for that.
> >
> > * As I said upthread, the patch makes code much more simple; I removed all
> > the changes to setrefs.c added by the partit
Hi,
On 2018-06-26 16:13:05 +0900, Michael Paquier wrote:
> I have been chewing for the last couple of days on this email from
> Horiguchi-san:
> https://www.postgresql.org/message-id/20180622.163312.254556300.horiguchi.kyot...@lab.ntt.co.jp
>
> As summarized, it is actually strange to be able to
On 2018-06-29 10:19:17 -0700, Andres Freund wrote:
> Hi,
>
> On 2018-06-29 13:56:12 +0200, Peter Eisentraut wrote:
> > On 6/29/18 13:07, amul sul wrote:
> > > This happens because of in fmgr_security_definer() function we are
> > > changing global variable SecurityRestrictionContext and in the
>
On 2018-Jul-03, Andres Freund wrote:
> I'm not clear to why this is a problem? Seems like either behaviour can
> be argued for. I don't really have an opinion either way. I'd just
> remove the item from the open items list, I don't think we need to hold
> up the release for it?
After reading this
On 2018-07-03 13:23:50 -0400, Alvaro Herrera wrote:
> On 2018-Jul-03, Andres Freund wrote:
>
> > I'm not clear to why this is a problem? Seems like either behaviour can
> > be argued for. I don't really have an opinion either way. I'd just
> > remove the item from the open items list, I don't thin
On 2018-Jul-03, Andres Freund wrote:
> On 2018-07-03 13:23:50 -0400, Alvaro Herrera wrote:
> > On 2018-Jul-03, Andres Freund wrote:
> >
> > > I'm not clear to why this is a problem? Seems like either behaviour can
> > > be argued for. I don't really have an opinion either way. I'd just
> > > remo
On Tue, Jun 26, 2018 at 6:25 AM, Amit Khandekar wrote:
> Added this into the July 2018 commitfest :
>
> https://commitfest.postgresql.org/18/1696/
It seems to me that it would probably be better to separate this into
two patches, because I think there are really two separate issues.
With regard t
Hello hackers,
I'd like to do this to postinit.c:
PerformAuthentication(MyProcPort);
+ AcceptInvalidationMessages();
InitializeSessionUserId(username, useroid);
Any objections? Motivation:
Many people use custom scripts, ldap2pg or other similar to
On Tue, Jul 03, 2018 at 01:51:48PM -0400, Alvaro Herrera wrote:
> Getting this fixed is +0.2 from me -- I'm not really on the side of this
> being a severe bug as all that.
This can also cause incorrect results for clients querying
pg_replication_slots when measuring bloat in pg_wal/, hence as thi
Attached 5th version of the patches, where minor refactoring of distance
handling was done (see below).
On 02.07.2018 19:06, Alexander Korotkov wrote:
Hi!
On Fri, Jun 29, 2018 at 5:37 PM Nikita Glukhov wrote:
On 06.03.2018 17:30, David Steele wrote:
I agree with Andres. Pushing this patch
@Peter: I was indexing the primary key of all the tables in tpc-ds. Some of
the fact tables has multiple columns as part of the primary key. Also, most
of them are numeric type.
On Mon, Jul 2, 2018 at 7:09 AM, Peter Geoghegan wrote:
> On Sun, Jul 1, 2018 at 5:19 PM, Tsunakawa, Takayuki
> wrote:
On 2018-Jul-04, Thomas Munro wrote:
> Hello hackers,
>
> I'd like to do this to postinit.c:
>
> PerformAuthentication(MyProcPort);
> + AcceptInvalidationMessages();
> InitializeSessionUserId(username, useroid);
>
> Any objections?
Is there a measur
On 05/17/2018 01:23 AM, Thomas Munro wrote:
On Tue, Mar 27, 2018 at 9:23 AM, Rady, Doug wrote:
pgbench11-ppoll-v12.patch
Hi Doug,
FYI this patch is trying and failing to use ppoll() on Windows:
https://ci.appveyor.com/project/postgresql-cfbot/postgresql/build/1.0.30
It's still failing
Hi,
On 2018-07-03 19:44:21 -0400, Alvaro Herrera wrote:
> On 2018-Jul-04, Thomas Munro wrote:
>
> > Hello hackers,
> >
> > I'd like to do this to postinit.c:
> >
> > PerformAuthentication(MyProcPort);
> > + AcceptInvalidationMessages();
> > Initiali
Hello,
As I asked at the PGCon developer meeting this year, we'd like to offer our
company's patents and patentapplications license to the PostgreSQL
community free of charge. If I heard correctly at that time, we could continue
this discussion during the unconference, but I missed tha
On Sat, Jun 30, 2018 at 6:27 AM Craig Ringer wrote:
>
> You can also gain a bit by running with wal_level = minimal. On newer
> version you can use UNLOGGED tables then convert them to logged, but that
> won't be an option for 9.4.
>
Curious to know more on this does with standby also its faster
On 4 July 2018 at 08:27, Tsunakawa, Takayuki wrote:
> Hello,
>
> As I asked at the PGCon developer meeting this year, we'd like to offer
> our company's patents and patentapplications license to the
> PostgreSQL community free of charge. If I heard correctly at that time, we
> could cont
On Tue, Jul 03, 2018 at 01:17:48AM -0400, Alvaro Herrera wrote:
> Let me review tomorrow.
Of course, please feel free.
--
Michael
signature.asc
Description: PGP signature
On Tue, Jul 03, 2018 at 01:51:48PM -0400, Alvaro Herrera wrote:
> On 2018-Jul-03, Andres Freund wrote:
>> Fair enough, but that's what a plain slot allows you as well, pretty
>> fundamentally, no? The precise point at which recycling will be blocked
>> will differer, sure.
ReplicationSlotsComputeR
(2018/07/04 1:35), Andres Freund wrote:
On 2018-06-22 10:58:28 -0400, Robert Haas wrote:
On Tue, Jun 19, 2018 at 8:46 AM, Etsuro Fujita
wrote:
Here is a patch for that.
I think this approach is going to run into trouble if the level at
which we have to apply the ConvertRowTypeExpr happens
>-Original Message-
>From: Peter Eisentraut [mailto:peter.eisentr...@2ndquadrant.com]
>Sent: Sunday, July 1, 2018 9:17 PM
>To: Ideriha, Takeshi/出利葉 健 ; pgsql-hackers
>
>Subject: Re: libpq example doesn't work
>
>On 27.06.18 08:29, Ideriha, Takeshi wrote:
>> When I tried to use libpq, I f
Hi.
I think we may have simply forgotten to do $subject in the following commit.
commit da6f3e45ddb68ab3161076e120e7c32cfd46d1db
Author: Alvaro Herrera
Date: Sat Apr 14 21:12:14 2018 -0300
Reorganize partitioning code
Attached a patch.
Thanks,
Amit
From 82113b74c2b385eb66be0c6be6e47aa63
On Wed, Jul 4, 2018 at 12:10 PM, Andres Freund wrote:
> On 2018-07-03 19:44:21 -0400, Alvaro Herrera wrote:
>> On 2018-Jul-04, Thomas Munro wrote:
>> > PerformAuthentication(MyProcPort);
>> > + AcceptInvalidationMessages();
>> > InitializeSessionUserId
On 2018-07-04 16:25:18 +1200, Thomas Munro wrote:
> @@ -745,6 +746,7 @@ InitPostgres(const char *in_dbname, Oid dboid, const char
> *username,
> /* normal multiuser case */
> Assert(MyProcPort != NULL);
> PerformAuthentication(MyProcPort);
> +
On Wed, Jul 04, 2018 at 04:25:18PM +1200, Thomas Munro wrote:
> Yeah, using "pgbench -c 8 -j 8 -T 60 --connect -S -M prepared
> postgres" I wasn't able to measure a significant difference on my
> laptop. The performance was equally terrible, at around 940 TPS +/-
> 10 including connection time. A
On Fri, Mar 30, 2018 at 10:06:46AM +0900, Kyotaro HORIGUCHI wrote:
> Hello. I found that c203d6cf81 hit this and this is the rebased
> version on the current master.
Okay, as this is visibly the oldest item in this commit fest, Andrew has
asked me to look at a solution which would allow us to def
Hi, hackers!
There is bunch of code in current GiST implementation checking for
GistTupleIsInvalid(). PostgreSQL since 9.1 do not create invalid tuples. Should
we support this tuples forever?
Invalid tuples were created in case of crash during GiST page split. They were
used as a recovery meas
Hi, hackers!
When execute sql with prepared protocol, read committed transaction will hold
backend_xmin until the end of the transaction.
Is this behavior normal?
Should read committed transaction release backend_xmin immediately after SQL
executing is completed? Just like
when executing sql w
On 2018/06/19 2:05, Tom Lane wrote:
> Amit Langote writes:
>> [ 0001-Open-partitioned-tables-during-Append-initialization.patch ]
>
> I took a look at this. While I'm in agreement with the general idea of
> holding open the partitioned relations' relcache entries throughout the
> query, I do not
61 matches
Mail list logo
