On Wed, Jun 8, 2011 at 10:45 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Pavan Deolasee pavan.deola...@gmail.com writes:
I first thought that analyze and vacuum can not run concurrently on the
same
table since they take a conflicting lock on the table. So even if we
ignore
the analyze process
from the previous post, should I
throw away the old commit fest entry and make the new one?
Regards,
--
Hitoshi Harada
aggjoin-20110609.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
I am installing postgresql using homebrew on OSX. I am getting strange
compilation errors. Googling did not help me in getting any lead to the
resolution. When I compile it on a standalone basis (without using brew) I
still get the same error. Compiling 9.1beta1 source package also gave me the
On Jun 8, 2011, at 9:13 AM, Robert Creager wrote:I've renamed /opt/local so it's not picked up, and change HEAD to build every 6 hours. Won't prove it doesn't happen though... If it appears to work for a bit, I can move /opt/local back and see what happens.Gack. ccache is in /opt/local/bin... I've
On Jun 7, 2011, at 11:32 PM, Tom Lane t...@sss.pgh.pa.us wrote:
But I tried make installcheck in plperl quite a few times with no
problems. (And yes, I tried some assorted settings of PERL_HASH_SEED,
as well as none at all.)
At this point I'm thinking that the perl you've got in
The attached patch adds contrib/sepgsql a cache mechanism for access
control decision of SELinux. It shall reduce the total number of
system call invocations to improve the performance on its access
controls.
In the current implementation, the sepgsql always raises a query to
SELinux in-kernel.
On Wed, Jun 8, 2011 at 20:22, Tom Lane t...@sss.pgh.pa.us wrote:
Is this really necessary now that we know about GROUP BY primary key?
You're right. I was just looking for something easy to hack on and
didn't put much thought into usefulness.
I'll try to do better next time. :)
Regards,
Marti
While testing this, I noticed another serious bug in the OldSerXidSLRU
handling: we never set the dirty-flag on any page. I believe the reason
we haven't bumped into this in testing before is that when a new page is
initialized, it's marked as dirty, so everything goes smoothly when we
modify
On Wed, Jun 8, 2011 at 6:43 PM, Joshua Berkus j...@agliodbs.com wrote:
Simon,
The point I have made is that I disagree with a feature freeze date
fixed ahead of time without regard to the content of the forthcoming
release. I've not said I disagree with feature freezes altogether,
which
On Thu, Jun 9, 2011 at 11:50 AM, Pavan Deolasee pavan.deola...@gmail.comwrote:
Ah, I see. Would there will be benefits if we can do some special handling
for cases where we know that ANALYZE is running outside a transaction block
and that its not going to invoke any user-defined functions ?
Hi hackers,
At first I've posted to pgsql-docs but there is no reply at present.
http://archives.postgresql.org/pgsql-docs/2011-06/msg6.php
So I post revised patch to pgsql-hackers, because the patch is for
documents under development for 9.1 beta2. Please let me know if this
was wrong
Hello list,
A little while ago time ago I posted about how my ... exciting
backup procedure caused occasional problems starting due to clog not
being big enough.
(http://archives.postgresql.org/pgsql-hackers/2011-04/msg01148.php) I
recently had a reproduction and a little bit of luck, and I
Oops, subject was incorrect. It should be [v9.2], not [v9.1]
2011/6/9 Kohei KaiGai kai...@kaigai.gr.jp:
The attached patch adds contrib/sepgsql a cache mechanism for access
control decision of SELinux. It shall reduce the total number of
system call invocations to improve the performance on
While reviewing the SLRU code in predicate.c again, I remembered this
old thread:
http://archives.postgresql.org/pgsql-hackers/2010-12/msg02374.php
SLRU has a limit of 64k segment files, because the files are named using
four hex digits like 00CE. Kevin's math shows that that's just enough
On Thu, Jun 9, 2011 at 12:39 AM, Jeevan Chalke
jeevan.cha...@enterprisedb.com wrote:
It's a problem, but without an efficient algorithm for Unicode case
folding, any fix we attempt to implement seems like it'll just be
moving the problem around.
Agree.
I read on other mail thread that
Dan Ports wrote:
On Wed, Jun 08, 2011 at 09:17:04PM -0500, Kevin Grittner wrote:
A patch is attached which just covers the predicate lock
acquisition, where a snapshot is available without too much pain.
There are two functions which acquire predicate locks where a
snapshot was not readily
Heikki Linnakangas wrote:
While testing this, I noticed another serious bug in the
OldSerXidSLRU handling: we never set the dirty-flag on any page.
Arg. I never noticed that there was such a thing, although in
retrospect I should have suspected it and gone hunting for it.
I believe the
On Wed, Jun 8, 2011 at 12:34, Radosław Smogura rsmog...@softperience.eu wrote:
After compilation I got big list of differences about binaries and other
files. You may see it in patch.
Hmm. Does this really affect just cygwin, and not also mingw? I know
msvc builds out-of-tree, but mingw
On Thu, Jun 9, 2011 at 7:46 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
While reviewing the SLRU code in predicate.c again, I remembered this old
thread:
http://archives.postgresql.org/pgsql-hackers/2010-12/msg02374.php
SLRU has a limit of 64k segment files, because the
On Thu, Jun 9, 2011 at 5:09 AM, Simon Riggs si...@2ndquadrant.com wrote:
I have asked that we maintain the Reasonableness we have always had
about how the feature freeze date was applied. An example of such
reasonableness is that if a feature is a few days late and it is
important, then it
On Thu, Jun 9, 2011 at 2:13 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Jun 9, 2011 at 5:09 AM, Simon Riggs si...@2ndquadrant.com wrote:
I have asked that we maintain the Reasonableness we have always had
about how the feature freeze date was applied. An example of such
reasonableness
Can we make this the last post on this topic please?
+1 :)
Thanks,
Pavan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Thu, 9 Jun 2011 14:12:59 +0200, Magnus Hagander wrote:
On Wed, Jun 8, 2011 at 12:34, Radosław Smogura
rsmog...@softperience.eu wrote:
After compilation I got big list of differences about binaries and
other
files. You may see it in patch.
Hmm. Does this really affect just cygwin, and not
On 06/09/2011 08:12 AM, Magnus Hagander wrote:
On Wed, Jun 8, 2011 at 12:34, Radosław Smogurarsmog...@softperience.eu wrote:
After compilation I got big list of differences about binaries and other
files. You may see it in patch.
Hmm. Does this really affect just cygwin, and not also mingw?
On Thu, 9 Jun 2011 14:12:59 +0200, Magnus Hagander wrote:
On Wed, Jun 8, 2011 at 12:34, Radosław Smogura
rsmog...@softperience.eu wrote:
After compilation I got big list of differences about binaries and
other
files. You may see it in patch.
Hmm. Does this really affect just cygwin, and not
=?UTF-8?Q?Rados=C5=82aw_Smogura?= rsmog...@softperience.eu writes:
On Thu, 9 Jun 2011 14:12:59 +0200, Magnus Hagander wrote:
What's nbproject?
Just configuration from some editor. It looks like any move in project
creates this entry in .gitignore
If you've got random third-party tools
On Thu, Jun 9, 2011 at 2:59 AM, Bhavin Kamani bhavinkam...@gmail.com wrote:
I am installing postgresql using homebrew on OSX. I am getting strange
compilation errors. Googling did not help me in getting any lead to the
resolution. When I compile it on a standalone basis (without using brew) I
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
It's awfully late in the release cycle, but how about we add another
digit to the filenames used by SLRU, to up the limit?
It's way too late for that kind of thing, unless you are saying that SSI
in and of itself is going to cause
Robert Haas robertmh...@gmail.com writes:
But now that I re-think about it, I guess what I'm confused about is
this code here:
if (ch = 'A' ch = 'Z')
ch += 'a' - 'A';
else if (IS_HIGHBIT_SET(ch) isupper(ch))
On Thu, Jun 9, 2011 at 10:07 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
But now that I re-think about it, I guess what I'm confused about is
this code here:
if (ch = 'A' ch = 'Z')
ch += 'a' - 'A';
Robert Haas robertmh...@gmail.com writes:
On Thu, Jun 9, 2011 at 10:07 AM, Tom Lane t...@sss.pgh.pa.us wrote:
We are relying on isupper() to not return true
when presented with a character fragment in a multibyte locale.
Based on Jeevan's original message, it seems like that's not always
the
On Thu, Jun 9, 2011 at 10:03 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
It's awfully late in the release cycle, but how about we add another
digit to the filenames used by SLRU, to up the limit?
It's way too late for that kind of
Excerpts from Robert Haas's message of mié jun 08 23:24:34 -0400 2011:
I did a brief literature search for papers on breaking the
WAL-serialization bottleneck today and hit upon this:
Aether: A Scalable Approach to Logging, Ryan Johnson, Ippokratis Pandis, et
al.
On Thu, Jun 9, 2011 at 15:40, Andrew Dunstan and...@dunslane.net wrote:
On 06/09/2011 08:12 AM, Magnus Hagander wrote:
On Wed, Jun 8, 2011 at 12:34, Radosław Smogurarsmog...@softperience.eu
wrote:
After compilation I got big list of differences about binaries and other
files. You may see
On Thu, Jun 9, 2011 at 10:15 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Jun 9, 2011 at 10:07 AM, Tom Lane t...@sss.pgh.pa.us wrote:
We are relying on isupper() to not return true
when presented with a character fragment in a multibyte locale.
On Thu, Jun 9, 2011 at 15:40, Radosław Smogura rsmog...@softperience.eu wrote:
On Thu, 9 Jun 2011 14:12:59 +0200, Magnus Hagander wrote:
On Wed, Jun 8, 2011 at 12:34, Radosław Smogura
rsmog...@softperience.eu wrote:
After compilation I got big list of differences about binaries and other
Robert Haas robertmh...@gmail.com writes:
So, speaking of that, aren't we supposed to wrap beta2 any minute now?
Yes. I'm expecting to do it this evening.
There are two open items listed on the open items page as blockers for beta2:
- error in information_schema.element_types view
On Thu, Jun 9, 2011 at 16:27, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
So, speaking of that, aren't we supposed to wrap beta2 any minute now?
Yes. I'm expecting to do it this evening.
There are two open items listed on the open items page as blockers for
On Thu, Jun 9, 2011 at 10:22 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
1. Subdivide XLOG insertion into three operations: (1) allocate space
in the log buffer, (2) copy the log records into the allocated space,
and (3) release the space to the buffer manager for eventual write to
On Thu, Jun 9, 2011 at 2:28 AM, Hitoshi Harada umi.tan...@gmail.com wrote:
BTW, as I changed title and design from the previous post, should I
throw away the old commit fest entry and make the new one?
Nah, just edit the existing entry and change the title.
Also add a link to the new patch, of
Excerpts from Robert Haas's message of jue jun 09 10:28:39 -0400 2011:
On Thu, Jun 9, 2011 at 10:22 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
1. Subdivide XLOG insertion into three operations: (1) allocate space
in the log buffer, (2) copy the log records into the allocated space,
On Thu, Jun 9, 2011 at 2:20 AM, Pavan Deolasee pavan.deola...@gmail.com wrote:
Ah, I see. Would there will be benefits if we can do some special handling
for cases where we know that ANALYZE is running outside a transaction block
and that its not going to invoke any user-defined functions ?
Robert Haas robertmh...@gmail.com wrote:
Tom Lane t...@sss.pgh.pa.us wrote:
aren't we supposed to wrap beta2 any minute now?
There are two open items listed on the open items page as blockers
for beta2:
- error in information_schema.element_types view definition (bug
5926)
- more
Robert Haas robertmh...@gmail.com writes:
On Thu, Jun 9, 2011 at 10:15 AM, Tom Lane t...@sss.pgh.pa.us wrote:
If we need to work around brain-dead isupper() tests, maybe the best
thing is to implement two versions of the loop:
if (encoding is single byte)
... loop as
I believe I have found a bug in libpq COPY handling with non-blocking
SSL connections. The bug manifests itself by dropping the connection
in PGputCopyData() with server closed the connection unexpectedly
message. The connection drop only occurs with nonblocking connections -
blocking connections
On 06/09/2011 10:25 AM, Magnus Hagander wrote:
Based on this list, a global exclude for *.exe and lib*dll.def
seems reasonable. Andrew, does that seem right to you as well?
That plus an entry in src/backend/.gitignore for /postgres.def.
cheers
andrew
--
Sent via pgsql-hackers mailing
Excerpts from Heikki Linnakangas's message of jue jun 09 04:56:41 -0400 2011:
Fortunately the fix is very simple, we just need to set the page_dirty
flag whenever we modify an slru page. But clearly this slru stuff needs
more testing. It's pretty hard to write good repeatable test cases for
Kevin Grittner kevin.gritt...@wicourts.gov writes:
The other pending patch relates to the false positives serialization
failures and funny-looking pg_lock entries from not ignoring
non-MVCC snapshots in SSI. I don't think Dan had any problem with
the patch I offered, but I wasn't sure what to
I am wondering if we shouldn't be asking ourselves a different
question: why is ANALYZE running long enough on your tables for this
to become an issue? How long is it taking?
The log file attached in the first post has the details; it's taking around 5
mins for the accounts table with
On Thu, Jun 9, 2011 at 10:34 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Robert Haas's message of jue jun 09 10:28:39 -0400 2011:
On Thu, Jun 9, 2011 at 10:22 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
1. Subdivide XLOG insertion into three operations: (1)
On Thu, Jun 9, 2011 at 10:52 AM, Pavan Deolasee
pavan.deola...@gmail.com wrote:
I am wondering if we shouldn't be asking ourselves a different
question: why is ANALYZE running long enough on your tables for this
to become an issue? How long is it taking?
The log file attached in the first
On Thu, Jun 9, 2011 at 10:38 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Jun 9, 2011 at 10:15 AM, Tom Lane t...@sss.pgh.pa.us wrote:
If we need to work around brain-dead isupper() tests, maybe the best
thing is to implement two versions of the loop:
Robert Haas robertmh...@gmail.com writes:
On Thu, Jun 9, 2011 at 10:52 AM, Pavan Deolasee
pavan.deola...@gmail.com wrote:
I am wondering if we shouldn't be asking ourselves a different
question: why is ANALYZE running long enough on your tables for this
to become an issue? How long is it
On 09-Jun-2011, at 8:29 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Jun 9, 2011 at 10:52 AM, Pavan Deolasee
pavan.deola...@gmail.com wrote:
I am wondering if we shouldn't be asking ourselves a different
question: why is ANALYZE running long
On Thu, Jun 9, 2011 at 10:37 AM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
There is this pending patch, without which there are infrequent
conditions under which the users could get a LOG level message and
accumulate files in pg_serial:
Alvaro Herrera alvhe...@commandprompt.com wrote:
Excerpts from Heikki Linnakangas's message of jue jun 09 04:56:41
-0400 2011:
Fortunately the fix is very simple, we just need to set the
page_dirty flag whenever we modify an slru page. But clearly this
slru stuff needs more testing. It's
Excerpts from Robert Haas's message of jue jun 09 10:55:45 -0400 2011:
On Thu, Jun 9, 2011 at 10:34 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Slower than sleeping? Consider that this doesn't need to be done for
each record insertion, only when you need to flush (maybe more than
Hello Greg, hello All,
This is my first post at Hackers, so sorry if I am been a noob here, but I
am pretty confused about
how to create the extension pg_buffercache.
First of all, I was trying to create using the old method by calling the
pg_buffercache--1.0.sql directly.
Then I discover the
On Thu, Jun 9, 2011 at 3:59 AM, Kohei KaiGai kai...@kaigai.gr.jp wrote:
The only modification by this patch to the core routine is a new
syscache for pg_seclabel system catalog. The SECLABELOID enables to
reference security label of the object using syscache interface.
I believe we decided
On Thu, Jun 9, 2011 at 11:13 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Robert Haas's message of jue jun 09 10:55:45 -0400 2011:
On Thu, Jun 9, 2011 at 10:34 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Slower than sleeping? Consider that this doesn't need to
Robert Haas robertmh...@gmail.com writes:
On Thu, Jun 9, 2011 at 10:15 AM, Tom Lane t...@sss.pgh.pa.us wrote:
If we need to work around brain-dead isupper() tests, maybe the best
thing is to implement two versions of the loop:
if (encoding is single byte)
That seems like a clear
On Thu, Jun 9, 2011 at 11:17 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Jun 9, 2011 at 10:15 AM, Tom Lane t...@sss.pgh.pa.us wrote:
If we need to work around brain-dead isupper() tests, maybe the best
thing is to implement two versions of the loop:
On 09.06.2011 17:46, Tom Lane wrote:
Kevin Grittnerkevin.gritt...@wicourts.gov writes:
The other pending patch relates to the false positives serialization
failures and funny-looking pg_lock entries from not ignoring
non-MVCC snapshots in SSI. I don't think Dan had any problem with
the patch
Robert Haas robertmh...@gmail.com writes:
One other problem I'm realizing: didn't Peter ask Bruce to revert the
change to make pg_upgrade ignore case differences in locale names, on
the grounds that it was not safe?
There was a hypothesis that it wasn't safe, but no very clear evidence
either
Magnus Hagander mag...@hagander.net Thursday 09 of June 2011 16:25:07
On Thu, Jun 9, 2011 at 15:40, Radosław Smogura rsmog...@softperience.eu
wrote:
On Thu, 9 Jun 2011 14:12:59 +0200, Magnus Hagander wrote:
On Wed, Jun 8, 2011 at 12:34, Radosław Smogura
rsmog...@softperience.eu wrote:
On 09.06.2011 15:50, Robert Haas wrote:
On Thu, Jun 9, 2011 at 7:46 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
While reviewing the SLRU code in predicate.c again, I remembered this old
thread:
http://archives.postgresql.org/pgsql-hackers/2010-12/msg02374.php
SLRU has a
Vinicius Abrahao wrote:
This is my first post at Hackers, so sorry if I am been a noob here,
but I am pretty confused about
how to create the extension pg_buffercache.
This list is for talking about development of new features, normally on
the latest development version of the software
Robert Haas wrote:
Well, if there are more tables that need vacuuming than there are
workers available at any given time, there will be a delay. We
probably don't keep track of that delay at present, but we could.
There are at least four interesting numbers to collect each time
autovacuum
Please do not piggyback on an unrelated thread to ask a question.
Start a new thread.
Vinicius Abrahao vinnix@gmail.com writes:
postgres=# CREATE EXTENSION pg_buffercache SCHEMA pg_catalog;
ERROR: syntax error at or near NO
This looks like a syntax error in the pg_buffercache--1.0.sql
Can someone explain why pg_stat_activity has a column named procpid and
not simply pid? 'pid' is that pg_locks uses, and 'procpid' is redundant
(proc-process-id). A mistake?
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB
2011/6/9 Robert Haas robertmh...@gmail.com:
On Thu, Jun 9, 2011 at 2:28 AM, Hitoshi Harada umi.tan...@gmail.com wrote:
BTW, as I changed title and design from the previous post, should I
throw away the old commit fest entry and make the new one?
Nah, just edit the existing entry and change
Robert Haas robertmh...@gmail.com wrote:
Kevin Grittner kevin.gritt...@wicourts.gov wrote:
There is this pending patch, without which there are infrequent
conditions under which the users could get a LOG level message
and accumulate files in pg_serial:
On Jun2, 2011, at 01:34 , Florian Pflug wrote:
On Jun2, 2011, at 00:02 , Noah Misch wrote:
On Wed, Jun 01, 2011 at 06:16:21PM +0200, Florian Pflug wrote:
Anyway, I'll try to come up with a patch that replaces
xmlSetGenericErrorFunc() with xmlSetStructuredErrorFunc().
Sounds sensible. Will
On Thu, Jun 9, 2011 at 16:40, Andrew Dunstan and...@dunslane.net wrote:
On 06/09/2011 10:25 AM, Magnus Hagander wrote:
Based on this list, a global exclude for *.exe and lib*dll.def
seems reasonable. Andrew, does that seem right to you as well?
That plus an entry in src/backend/.gitignore
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
On 09.06.2011 15:50, Robert Haas wrote:
And I would guess that there's a lot more interest in raising BLCKSZ
than lowering it. It might not be a bad idea to adopt the fix you
propose anyway, but it doesn't seem urgent.
I guess
Excerpts from Tom Lane's message of mié jun 08 21:50:22 -0400 2011:
Robert Haas robertmh...@gmail.com writes:
I think it'd be really useful to expose some more data in this area
though. One random idea is - remember the time at which a table was
first observed to need vacuuming. Clear the
Bruce Momjian br...@momjian.us writes:
Can someone explain why pg_stat_activity has a column named procpid and
not simply pid? 'pid' is that pg_locks uses, and 'procpid' is redundant
(proc-process-id). A mistake?
Mistake or not, it's about half a dozen releases too late to change it.
* Kohei KaiGai (kai...@kaigai.gr.jp) wrote:
The only modification by this patch to the core routine is a new
syscache for pg_seclabel system catalog. The SECLABELOID enables to
reference security label of the object using syscache interface.
Perhaps I'm missing it, but.. why is this necessary
On Wed, Jun 8, 2011 at 11:30 PM, Merlin Moncure mmonc...@gmail.com wrote:
The heap pages that have been marked this way may or may not have to
be off limits from the backend other than the one that did the
marking, and if they have to be off limits logically, there may be no
realistic path to
2011/6/9 Robert Haas robertmh...@gmail.com:
On Thu, Jun 9, 2011 at 3:59 AM, Kohei KaiGai kai...@kaigai.gr.jp wrote:
The only modification by this patch to the core routine is a new
syscache for pg_seclabel system catalog. The SECLABELOID enables to
reference security label of the object using
On Thu, Jun 9, 2011 at 11:54 AM, Bruce Momjian br...@momjian.us wrote:
Can someone explain why pg_stat_activity has a column named procpid and
not simply pid? 'pid' is that pg_locks uses, and 'procpid' is redundant
(proc-process-id). A mistake?
Well, we refer to the slots that backends use
Alvaro Herrera alvhe...@commandprompt.com writes:
In any case, given the rebalancing feature of vacuum_cost_delay (which
increases the delay the more workers there are), the only solution to
the problem of falling behind is reducing the delay parameter. If you
just add more workers, they
Robert Haas robertmh...@gmail.com writes:
[ lots of interesting stuff about WAL optimization snipped ]
... Second, they aren't really using locks, unless you count
bus locks - they appear to have implemented most or all of it via
CAS-based lock-free algorithms, which is probably
2011/6/9 Stephen Frost sfr...@snowman.net:
* Kohei KaiGai (kai...@kaigai.gr.jp) wrote:
The only modification by this patch to the core routine is a new
syscache for pg_seclabel system catalog. The SECLABELOID enables to
reference security label of the object using syscache interface.
Perhaps
Excerpts from Tom Lane's message of jue jun 09 09:42:02 -0400 2011:
=?UTF-8?Q?Rados=C5=82aw_Smogura?= rsmog...@softperience.eu writes:
On Thu, 9 Jun 2011 14:12:59 +0200, Magnus Hagander wrote:
What's nbproject?
Just configuration from some editor. It looks like any move in project
On Mon, May 23, 2011 at 16:49, MauMau maumau...@gmail.com wrote:
From: Kevin Grittner kevin.gritt...@wicourts.gov
MauMau maumau...@gmail.com wrote:
Make pg_ctl's -s option suppress informational event logging.
This will ultimately be up to a committer (and I'm not one), but to
me it seems
On Thu, Jun 9, 2011 at 12:25 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Tom Lane's message of mié jun 08 21:50:22 -0400 2011:
Robert Haas robertmh...@gmail.com writes:
I think it'd be really useful to expose some more data in this area
though. One random idea is -
Alvaro Herrera alvhe...@commandprompt.com writes:
I agree with that, though the *dll.def files are ours and probably
deserve a global .gitignore entry.
Agreed, and that's done.
As for executables, I think the local .gitignore files in each subdir
should be tweaked so that they catch the .exe
Robert Haas wrote:
On Wed, Jun 1, 2011 at 7:07 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
Excerpts from Robert Haas's message of mi? jun 01 18:22:56 -0400 2011:
ISTM that it would be useful to run postgres in a mode where it
doesn't actually
Andrew Dunstan wrote:
On 06/08/2011 02:29 PM, Tom Lane wrote:
Should we consider doing $SUBJECT? Given the plan to branch off 9.1
after we make the beta release, I think it's now or never for a second
pgindent run for 9.1.
OK, I have made sure the list on
Bruce Momjian br...@momjian.us writes:
Andrew Dunstan wrote:
On 06/08/2011 02:29 PM, Tom Lane wrote:
Should we consider doing $SUBJECT? Given the plan to branch off 9.1
after we make the beta release, I think it's now or never for a second
pgindent run for 9.1.
OK, I have made sure the
On Thu, Jun 9, 2011 at 12:52 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
[ lots of interesting stuff about WAL optimization snipped ]
... Second, they aren't really using locks, unless you count
bus locks - they appear to have implemented most or all of it
Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
Andrew Dunstan wrote:
On 06/08/2011 02:29 PM, Tom Lane wrote:
Should we consider doing $SUBJECT? Given the plan to branch off 9.1
after we make the beta release, I think it's now or never for a second
pgindent run for 9.1.
OK,
Excerpts from Tom Lane's message of jue jun 09 12:57:46 -0400 2011:
Alvaro Herrera alvhe...@commandprompt.com writes:
I agree with that, though the *dll.def files are ours and probably
deserve a global .gitignore entry.
Agreed, and that's done.
Oh, I see ... I haven't gotten the commit
On Thu, Jun 9, 2011 at 12:39 PM, Kohei KaiGai kai...@kaigai.gr.jp wrote:
2011/6/9 Robert Haas robertmh...@gmail.com:
On Thu, Jun 9, 2011 at 3:59 AM, Kohei KaiGai kai...@kaigai.gr.jp wrote:
The only modification by this patch to the core routine is a new
syscache for pg_seclabel system catalog.
On Thu, Jun 9, 2011 at 12:54 PM, Kohei KaiGai kai...@kaigai.gr.jp wrote:
2011/6/9 Stephen Frost sfr...@snowman.net:
* Kohei KaiGai (kai...@kaigai.gr.jp) wrote:
The only modification by this patch to the core routine is a new
syscache for pg_seclabel system catalog. The SECLABELOID enables to
Robert Haas wrote:
On Thu, Jun 9, 2011 at 11:54 AM, Bruce Momjian br...@momjian.us wrote:
Can someone explain why pg_stat_activity has a column named procpid and
not simply pid? ?'pid' is that pg_locks uses, and 'procpid' is redundant
(proc-process-id). ?A mistake?
Well, we refer to the
Robert Haas robertmh...@gmail.com writes:
On Thu, Jun 9, 2011 at 11:17 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Hmm ... while the above is easy enough to do in the backend, where we
can look at pg_database_encoding_max_length, we have also got instances
of this coding pattern in
Hi,
on shdepReassignOwned() we have this message, which is obviously wrong
we are not dropping objects just reassigning them...
ereport(ERROR,
(errcode(ERRCODE_DEPENDENT_OBJECTS_STILL_EXIST),
errmsg(cannot drop objects owned
by %s
On Thu, Jun 09, 2011 at 07:06:18AM -0500, Kevin Grittner wrote:
Sounds reasonable, but why did you pass the snapshot to the
PredicateLockPage() call but not the PredicateLockRelation() call?
Oversight?
Yep, just an oversight; long day yesterday. I'll fix the patch shortly
(unless you can get
1 - 100 of 155 matches
Mail list logo
