One solution that is striking me is
1. I'll create one background worker and will initialise DSA in it.
2. If there are any callbacks available for client open/close connections,
i'll attach/detach to the DSA in those callbacks.
But i'm not sure there are such callbacks available. If such call
Hi,
As Michael said, i'm creating DSA too early. Shared_Preload libraries are
loading prior to memory related stuff.
But i'm totally clueless how to solve my use case.
Please help me with any work around.
Thanks & Best Regards,
- Mahi
On Tue, May 23, 2017 at 5:52 PM, Mahi Gurram wrote:
> Hi
On Mon, May 22, 2017 at 6:32 AM, Thomas Munro
wrote:
> On Mon, May 22, 2017 at 4:10 AM, Dmitry Dolgov <9erthali...@gmail.com> wrote:
>> I'm wondering about status of this patch and how can I try it out?
>
> Hi Dmitry, thanks for your interest.
>
>>> On 3 January 2017 at 02:43, Thomas Munro
>>> wr
On 2017-05-23 22:47:07 -0400, Robert Haas wrote:
> On Mon, May 22, 2017 at 11:42 AM, Andres Freund wrote:
> > Ooops.
> >
> > Two issues: Firstly, we get a value smaller than seqmin, obviously
> > that's not ok. But even if we'd error out, it'd imo still not be ok,
> > because we have a command tha
I have written the following sed script to convert regular Postgres
email message URLs to their shorter form for commit messages:
sed 's;http\(s\?\)://www\.postgresql\.org/message-id/;http\1://postgr.es/m/;gi'
in case this is helpful to anyone.
--
Bruce Momjian http://momjian.us
E
On Mon, May 22, 2017 at 11:42 AM, Andres Freund wrote:
> Ooops.
>
> Two issues: Firstly, we get a value smaller than seqmin, obviously
> that's not ok. But even if we'd error out, it'd imo still not be ok,
> because we have a command that behaves partially transactionally
> (keeping the seqmax/min
On Tue, May 23, 2017 at 9:45 AM, Tom Lane wrote:
> Robert Haas writes:
>> Just out of curiosity, what happens if you try it with the attached patch?
>
> Surely that's pretty unsafe?
Yes. I was just curious to see whether it would work. I think what
we need to do is teach pqsignal() to block al
2017-05-04 22:26 GMT-03:00 Andres Freund :
> At least I was a bit more optimistic that we'd get a decent json plugin
> into care soon-ish. While there was some initial work towards that, it
> unfortunately stalled at some point.
>
> That was my initial idea but there wasn't some interest at that
Rebuilding Perl and all it’s related ports fixed it.
Dealing with the FreeBSD folks on what all we (FreeBSD) need to put in
/usr/ports/UPDATING and / or
/usr/src/UPDATING
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerc
Heikki Linnakangas writes:
> On 05/20/2017 01:48 PM, Tom Lane wrote:
>> Attached is a proposed patch. I'm vacillating on whether to
>> back-patch this --- it will fix a reported bug, but it seems
>> at least somewhat conceivable that it will also break cases
>> that were working acceptably before
Hello,
On Mon, May 22, 2017 at 11:29 AM, Ashutosh Bapat <
ashutosh.ba...@enterprisedb.com> wrote:
> On Mon, May 22, 2017 at 7:27 AM, Beena Emerson
> wrote:
> Would it be more readable if this reads as NOT
> (constraint_for_partition_1 || constraint_for_partition_2 ||
> constraint_for_partition_3
Hi
I am watching this patch - it looks so there are not problems. I found only
issue in documentation - new CASE expression is not documented.
Regards
Pavel
Looks like the upgrade of this machine to the inode64 commit of FreeBSD busted
stuff.
I’m rebuilding perl and all the ports to see if that fixes it.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 17716
Hi,
Following code in function get_qual_for_list(partition.c) is not reachable.
else
result = list_make1(opexpr);
Attached is the patch that removes this dead code.
Regards,
Jeevan Ladhe
partition_remove_dead_code.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-
On 23/05/17 19:45, Andres Freund wrote:
>
>
> On May 23, 2017 1:42:41 PM EDT, Petr Jelinek
> wrote:
>> Hi,
>>
>> so this didn't really move anywhere AFAICS, do we think the approach
>> I've chosen is good or do we want to do something else here?
>
> Can you add it to the open items list?
>
D
On 20/04/17 21:33, Peter Eisentraut wrote:
> On 4/18/17 13:18, Tom Lane wrote:
>> I think you're thinking about it wrong. To my mind the issue is that
>> there should be some generic way to determine that a bgworker process
>> is or is not laboring on behalf of an identifiable user. It's great
>>
On May 23, 2017 1:42:41 PM EDT, Petr Jelinek
wrote:
>Hi,
>
>so this didn't really move anywhere AFAICS, do we think the approach
>I've chosen is good or do we want to do something else here?
Can you add it to the open items list?
Andres
--
Sent from my Android device with K-9 Mail. Please ex
Hi,
so this didn't really move anywhere AFAICS, do we think the approach
I've chosen is good or do we want to do something else here?
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing li
Hi hackers,
We have some problems on our production with hint bits and frozen tuples.
More and more following errors began to appear on master after switchover:
ERROR: 58P01: could not access status of transaction 1952523525
DETAIL: Could not open file "pg_clog/0746": No such file or directory.
Good day, everyone.
It is just proposal.
Main concern: allow compressed toast to be seekable.
Since every chunk compressed separately, toast_fetch_datum_slice can
fetch each slice separately as with EXTERNAL storage.
Attached patch is couple of new column storage types:
- EXTSEEKABLE - like exte
Robert Haas writes:
> Just out of curiosity, what happens if you try it with the attached patch?
Surely that's pretty unsafe?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgr
Thanks, Andres,
I have tried to fix all of your comments. One important change has
happened with this patch is previously we used to read one block info
structure at a time and load it. But now we read all of them together
and load it into as DSA and then we distribute the block infos to the
subgr
On 2017-05-23 10:49:54 +, Neha Khatri wrote:
> On Tue, 23 May 2017 at 10:55 am, Alvaro Herrera
> wrote:
>
> > Neha Khatri wrote:
> > > On Tue, May 23, 2017 at 10:26 AM, Michael Paquier <
> > michael.paqu...@gmail.com
> >
> > > > There is no wal_level higher than logical, so the current sense
On 05/23/2017 06:25 PM, Robert Haas wrote:
Just out of curiosity, what happens if you try it with the attached patch?
Thanks, issue seems to be fixed after applying your patch.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-h
On Tue, May 23, 2017 at 1:46 AM, tushar wrote:
> On 03/29/2017 12:06 AM, Tom Lane wrote:
>>
>> Hm ... I don't see a crash here, but I wonder whether you have parameters
>> set that would cause this query to be run as a parallel query? Because
>> pg_rotate_logfile() is marked as parallel-safe in p
Hi Michael,
Thanks for your response.
All i'm building is In-Memory Index as an extension over Postgres.
Postgres Indexes will get Insert calls and Read calls from various
processes(typically client/connection process - forked processes to
postmaster process). Hence i have to maintain my In-Memo
On Sat, May 20, 2017 at 5:56 PM, Noah Misch wrote:
> On Sat, Apr 15, 2017 at 02:30:18PM -0700, Andres Freund wrote:
>> On 2017-04-15 17:24:54 -0400, Tom Lane wrote:
>> > Andres Freund writes:
>> > > On 2017-04-15 17:09:38 -0400, Tom Lane wrote:
>> > >> Why doesn't Windows' ability to map the segm
On Tue, May 23, 2017 at 4:41 PM, Amit Kapila wrote:
> Isn't this point contradictory? Basically, on one side you are
> suggesting to calculate additional workers (work_remaining) based on
> selectivity and on another side you are saying that it will fix
> estimation errors. IIUC, then you are t
On Tue, May 23, 2017 at 6:42 AM, Mahi Gurram wrote:
> I'm building In-Memory index extension for Postgres, for which i'm trying to
> use DSA. But ended with some issues, as it is not allowing me to create
> DSA(Dynamic Shared Area) in _PG_init function.
>
> Please refer my_PG_init code below:
>>
>
On Tue, May 23, 2017 at 6:36 AM, Heikki Linnakangas wrote:
> On 05/22/2017 10:11 PM, Vaishnavi Prabakaran wrote:
>>
>> On Mon, May 22, 2017 at 5:10 PM, Michael Paquier
>>
>> wrote:
>>
>>> If the protocol version is SSL
>>> 3.0 or TLS 1.0, this result code is returned only if a closure alert
>>> h
On Mon, May 22, 2017 at 2:54 PM, Rafia Sabih
wrote:
> On Wed, May 17, 2017 at 2:57 PM, Amit Kapila wrote:
>> On Tue, May 16, 2017 at 2:14 PM, Ashutosh Bapat
>> wrote:
>>> On Mon, May 15, 2017 at 9:23 PM, Robert Haas wrote:
>>>
>>> Also, looking at the patch, it doesn't look like it take enough
Thank you all for your responses to help me out.
The below code worked for me... pasting it here (May be helpful for someone)
Relation heap;
> ItemPointer ht_ctid;
> heap = heap_open(50620, AccessShareLock); /* 50620 - Table/Relation Oid -
> Hardcoded for better understanding */
ScanKeyInit(&ske
On 17 May 2017 at 14:30, Robert Haas wrote:
> On Tue, May 16, 2017 at 9:20 PM, Andrew Dunstan
> wrote:
>> Inheriting variables from the environment is a part of make by design.
>> We have PG_PROVE_FLAGS for our own forced settings.
>
> I don't buy this argument. We've had previous cases where we
On 05/20/2017 01:48 PM, Tom Lane wrote:
Attached is a proposed patch. I'm vacillating on whether to
back-patch this --- it will fix a reported bug, but it seems
at least somewhat conceivable that it will also break cases
that were working acceptably before. Thoughts?
+1 for back-patching. If
On Tue, 23 May 2017 at 10:55 am, Alvaro Herrera
wrote:
> Neha Khatri wrote:
> > On Tue, May 23, 2017 at 10:26 AM, Michael Paquier <
> michael.paqu...@gmail.com
>
> > > There is no wal_level higher than logical, so the current sense looks
> > > perfectly fine to me.
> >
> > If there is no wal_leve
Hello everyone,
I'm building In-Memory index extension for Postgres, for which i'm trying
to use DSA. But ended with some issues, as it is not allowing me to create
DSA(Dynamic Shared Area) in _PG_init function.
Please refer my_PG_init code below:
> void
> _PG_init(void)
> {
> area = dsa_create(
On 05/22/2017 10:11 PM, Vaishnavi Prabakaran wrote:
On Mon, May 22, 2017 at 5:10 PM, Michael Paquier
wrote:
If the protocol version is SSL
3.0 or TLS 1.0, this result code is returned only if a closure alert
has occurred in the protocol, i.e. if the connection has been closed
cleanly. Note tha
On 05/22/2017 03:10 AM, Michael Paquier wrote:
Hi all,
When attempting to connect using password authentication through SSL,
the backend will complain in its log with the following entry before
calling sendAuthRequest(), which asks the client for a password:
LOG: could not receive data from cli
Hi, hackers!
Here's a small patch that implements fetch function necessary for
Index Only Scans that use cube data type.
I reuse function g_cube_decompress() instead of creating new function
g_cube_fetch().
Essentially, they both have to detoast data.
How do you think, is it better to create a sh
Hi,
ALTER SUBSCRIPTION ..SET PUBLICATION refresh is removing all
the attached subscription('s).
X Machine -
s=# create table t(n int);
CREATE TABLE
s=# create table t1(n int);
CREATE TABLE
s=# create publication pub for table t,t1;
CREATE PUBLICATION
s=#
Y Machine -
s=# create table t(n
On 23 May 2017 at 07:26, Euler Taveira wrote:
>
> ReplicationSlotValidateName() should be called in
parse_subscription_options() to avoid a pilot error.
> IMHO we should prevent a future error (use of invalid slot name).
Yes, I see now. I assume this little patch should be enough for that.
diff -
Hi,
> I am looking at ECPG source code. In the "ecpg/ecpglib/pg_type.h" file I
> have seen following comment:
>
> ** keep this in sync with src/include/catalog/pg_type.h*
>
> But I think the "ecpg/ecpglib/pg_type.h" file is currently not synced
> with the above file.
>
> I have added the remain
On 22 May 2017 at 16:10, David Rowley wrote:
> I also just noticed that I don't think I've got ANTI join cases
> correct in the patch I sent. I'll look at that now.
I've attached an updated patch.
This one is much less invasive than my original attempt.
There are two fundamental changes here:
43 matches
Mail list logo
