On Mon, Feb 9, 2015 at 4:56 PM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Feb 9, 2015 at 5:38 AM, Magnus Hagander mag...@hagander.net
wrote:
On Mon, Feb 9, 2015 at 11:09 AM, Marco Nenciarini
marco.nenciar...@2ndquadrant.it wrote:
Il 08/02/15 17:04, Magnus Hagander ha scritto:
On 13 February 2015 at 20:52, Michael Paquier michael.paqu...@gmail.com
wrote:
On Sun, Nov 23, 2014 at 8:23 PM, David Rowley dgrowle...@gmail.com
wrote:
As the patch stands there's still a couple of FIXMEs in there, so there's
still a bit of work to do yet.
Comments are welcome
Hm, if
On Sat, Feb 7, 2015 at 1:59 PM, Magnus Hagander mag...@hagander.net wrote:
On Sat, Feb 7, 2015 at 1:53 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Sat, Feb 7, 2015 at 1:02 AM, Jeff Janes jeff.ja...@gmail.com
wrote:
I'd like the ability to add a
There does not seem to be a delete button, so marking as rejected due to this
now being a duplicate entry for this patch.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Martijn van Oosterhout klep...@svana.org writes:
On Thu, Feb 12, 2015 at 08:52:56AM -0500, Robert Haas wrote:
BTW, I'm not all that thrilled with the deserialized object terminology.
I found myself repeatedly tripping up on which form was serialized and
which de-. If anyone's got a better
On 2015-02-14 17:25:00 +, Kevin Grittner wrote:
Andres Freund and...@2ndquadrant.com wrote:
Imagine what happens in LockBufferForCleanup() when
ProcWaitForSignal() returns spuriously - something it's
documented to possibly do (and which got more likely with the new
patches). In the
Andres Freund and...@2ndquadrant.com wrote:
On 2015-02-14 17:25:00 +, Kevin Grittner wrote:
I think we should simply move the
buf-flags = ~BM_PIN_COUNT_WAITER (Inside LockBuffer)
I think you meant inside UnpinBuffer?
No, LockBufferHdr. What I meant was that the pincount can only be
On Sat, Feb 14, 2015 at 10:45 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Martijn van Oosterhout klep...@svana.org writes:
On Thu, Feb 12, 2015 at 08:52:56AM -0500, Robert Haas wrote:
BTW, I'm not all that thrilled with the deserialized object terminology.
I found myself repeatedly tripping up on
On 2015-02-12 18:16:37 -0500, Tom Lane wrote:
I wrote:
Christoph Berg c...@df7cb.de writes:
gcc5 is lurking in Debian experimental, and it's breaking initdb.
Yeah, I just heard the same about Red Hat as well:
https://bugzilla.redhat.com/show_bug.cgi?id=1190978
Not clear if it's an
Asif Naeem anaeem...@gmail.com writes:
It is been observed on RANDOMIZE_ALLOCATED_MEMORY enabled PG95 build that
chkpass is failing because of uninitialized memory and seems showing false
alarm.
It's not a false alarm, unfortunately, because chkpass_in actually does
give different results from
Andres Freund and...@2ndquadrant.com wrote:
I don't think it's actually 675333 at fault here. I think it's a
long standing bug in LockBufferForCleanup() that can just much
easier be hit with the new interrupt code.
The patches I'll be posting soon make it even easier to hit, which
is why I
On Sat, Feb 14, 2015 at 7:29 AM, Magnus Hagander mag...@hagander.net wrote:
Ok, I've pushed an attempt at doing this.
For each mailthread, you can now create annotations. Each annotation is
connected to a mail in the thread, and has a free text comment field. The
message will then
Robert Haas robertmh...@gmail.com writes:
On Sat, Feb 14, 2015 at 10:45 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Martijn van Oosterhout klep...@svana.org writes:
The words that sprung to mind for me were: packed/unpacked.
Trouble is that we're already using packed with a specific connotation
SASL was done by many of the same people who did GSSAPI. It's main practical
advantages are that it supports password-based mechanisms (in addition to
GSSAPI/krb5), and that it’s more explicitly pluggable than GSSAPI is.
The password mechanism is simple enough that it's frequently implemented
Peter Eisentraut pete...@gmx.net writes:
Here is a scenario:
./configure --prefix=/usr/local/pgsql/9.4.1
make
make install
ln -s 9.4.1 /usr/local/pgsql/9.4
PATH=/usr/local/pgsql/9.4/bin:$PATH
And then when 9.4.2 comes out, the symlink is updated.
I think this sort of setup in variations
Andres Freund and...@2ndquadrant.com writes:
I don't think it's actually 675333 at fault here. I think it's a
long standing bug in LockBufferForCleanup() that can just much easier be
hit with the new interrupt code.
Imagine what happens in LockBufferForCleanup() when ProcWaitForSignal()
On 2/13/15 3:34 PM, David Fetter wrote:
On Fri, Feb 13, 2015 at 03:13:11PM -0600, Jim Nasby wrote:
On 2/10/15 2:04 PM, David Fetter wrote:
Yeah, but people expect to be able to partition on ranges that are not
all of equal width. I think any proposal that we shouldn't support
that is the kiss
On Fri, Feb 13, 2015 at 3:32 AM, happy times guangzhouzh...@qq.com wrote:
I didn’t find any convenient way to restrict access to PostgreSQL databases
to be read-only for all users. I need it in following scenarios:
A) Planned switch-over from master to slave. We want to minimize impact
within
The comments say say that we must use an MVCC snapshot here, but
they don't explain why it should be one retrieved via
GetTransactionSnapshot() rather than GetActiveSnapshot() or
GetLatestSnapshot() or GetCatalogSnapshot(). The comments also refer
the reader to catalog/pg_enum.c for more details,
On 2/14/15 11:42 AM, Robert Haas wrote:
On Sat, Feb 14, 2015 at 7:29 AM, Magnus Hagander mag...@hagander.net wrote:
Ok, I've pushed an attempt at doing this.
For each mailthread, you can now create annotations. Each annotation is
connected to a mail in the thread, and has a free text comment
We have a customer who was unable to migrate from a well-known
commercial database product to pg because they have a very large
software base that holds cursors open for very long periods of
time, preventing GlobalXmin values from advancing, leading to
bloat. They have a standard test that
On 02/10/2015 02:21 AM, Peter Geoghegan wrote:
On Fri, Feb 6, 2015 at 1:51 PM, Bruce Momjian br...@momjian.us wrote:
Other than the locking part, the biggest part of this patch is adjusting
things so that an INSERT can change into an UPDATE.
Thanks for taking a look at it. That's somewhat
Robert Haas robertmh...@gmail.com writes:
I think this is probably a holdover from before the death of
SnapshotNow, and that we should just pass NULL to
systable_beginscan_ordered() here, the same as we do for other catalog
accesses. Barring objections, I'll go make that change.
Seems
On Sat, Feb 14, 2015 at 5:12 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I think this is probably a holdover from before the death of
SnapshotNow, and that we should just pass NULL to
systable_beginscan_ordered() here, the same as we do for other catalog
On 2/14/15 3:14 PM, Robert Haas wrote:
On Fri, Feb 13, 2015 at 3:32 AM, happy times guangzhouzh...@qq.com wrote:
I didn’t find any convenient way to restrict access to PostgreSQL databases
to be read-only for all users. I need it in following scenarios:
A) Planned switch-over from master to
Jim Nasby jim.na...@bluetreble.com writes:
On 2/14/15 3:14 PM, Robert Haas wrote:
Although I like the idea, it's not clear to me how to implement it.
Throw an error in AssignTransactionId/GetNewTransactionId?
A whole lot depends on what you choose to mean by read only. If it
means the same
This patch is related to the Reduce pinning in btree indexes
patch submitted here:
http://www.postgresql.org/message-id/721615179.3351449.1423959585771.javamail.ya...@mail.yahoo.com
That describes how they evolved and how they relate; I won't
duplicate that here.
Unlike the other patch, this
Kevin Grittner kgri...@ymail.com writes:
What this patch does is add a GUC call old_snapshot_threshold. It
defaults to -1, which leaves behavior matching unpatched code.
Above that it allows tuples to be vacuumed away after the number of
transaction IDs specified by the GUC have been
On 8/31/14 5:36 AM, Fabien COELHO wrote:
Running make -j2 check-world does not work because initdb is not
found by pg_regress. but make -j1 check-world does work fine. It
seems that some dependencies might be missing and there is a race
condition between temporary install and running some
Peter Eisentraut pete...@gmx.net writes:
On 8/31/14 5:36 AM, Fabien COELHO wrote:
Running make -j2 check-world does not work because initdb is not
found by pg_regress. but make -j1 check-world does work fine. It
seems that some dependencies might be missing and there is a race
condition
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kgri...@ymail.com writes:
What this patch does is add a GUC call old_snapshot_threshold. It
defaults to -1, which leaves behavior matching unpatched code.
Above that it allows tuples to be vacuumed away after the number of
transaction IDs
I've posted a couple of messages over the last few weeks about the work
I've been doing on the pg_audit extension. The lack of response could
be due to either universal acclaim or complete apathy, but in any case I
think this is a very important topic so I want to give it another try.
I've
Attached is a patch to provide a number of very useful facilities to
jsonb that people have asked for. These are based on work by Dmitry
Dolgov in his jsonbx extension, but I take responsibility for any bugs.
The facilities are:
new operations:
concatenation:jsonb || jsonb - jsonb
When managing configuration changes through automatic systems like Chef
or Puppet, there is a problem: How do you manage changes requiring a
restart?
Generally, you'd set it up so that when a configuration file is changed,
the server is reloaded. But for settings that require a restart, well,
I
I understand that on Windows, you can use forward slashes in path names
interchangeably with backward slashes (except possibly in the shell). I
have developed the attached patch to change the msvc build code to use
forward slashes consistently. Together with the other attached patch,
which is an
35 matches
Mail list logo
