On Tue, 3 Mar 2015 11:15:13 -0500
Bruce Momjian br...@momjian.us wrote:
On Tue, Oct 14, 2014 at 01:21:53PM -0400, Bruce Momjian wrote:
On Tue, Oct 14, 2014 at 09:20:22AM -0700, Jeff Janes wrote:
On Mon, Oct 13, 2014 at 12:11 PM, Bruce Momjian br...@momjian.us wrote:
I looked
On Mon, Mar 30, 2015 at 8:54 PM, Jeff Janes jeff.ja...@gmail.com wrote:
After freeing up the rows at the end of the table so it is eligible for
truncation, then running a manual VACUUM to actually release the space, I
kept running into the problem that the truncation scan was consistently
On Tue, 31 Mar 2015 08:24:15 +0200
Jehan-Guillaume de Rorthais j...@dalibo.com wrote:
On Tue, 3 Mar 2015 11:15:13 -0500
Bruce Momjian br...@momjian.us wrote:
On Tue, Oct 14, 2014 at 01:21:53PM -0400, Bruce Momjian wrote:
On Tue, Oct 14, 2014 at 09:20:22AM -0700, Jeff Janes wrote:
On
On Tue, Mar 31, 2015 at 3:42 PM, Jeff Janes jeff.ja...@gmail.com wrote:
On Mon, Mar 30, 2015 at 8:54 PM, Jeff Janes jeff.ja...@gmail.com wrote:
After freeing up the rows at the end of the table so it is eligible for
truncation, then running a manual VACUUM to actually release the space, I
Le lundi 30 mars 2015 18:45:41 Jim Nasby a écrit :
On 3/30/15 5:46 AM, Ronan Dunklau wrote:
Hello hackers,
I've tried my luck on pgsql-bugs before, with no success, so I report
these
problem here.
The documentation mentions the following limits for sizes:
Maximum Field Size
On Tue, Mar 31, 2015 at 9:59 AM, Peter Eisentraut pete...@gmx.net wrote:
There are some small issues with the pg_rewind tests.
This technique
check: all
$(prove_check) :: local
$(prove_check) :: remote
for passing arguments to prove does not work with the tools included
On 03/30/2015 09:57 PM, Peter Geoghegan wrote:
On Mon, Mar 30, 2015 at 7:50 PM, Joshua D. Drake j...@commandprompt.com wrote:
We have a database that has run into this problem. The version is 9.1.15 on
Linux. I note in this thread:
hi all,
back in
2011(http://www.postgresql.org/message-id/1305138588.8811.3.ca...@vanquo.pezone.net),
an question the same as this one was asked
the anwser was :
I think they're very useful on views, but I
couldn't think of a use-case for having them on tables. ISTM that
anything an INSTEAD
2015-03-29 21:20 GMT+02:00 Pavel Stehule pavel.steh...@gmail.com:
2015-03-29 20:27 GMT+02:00 Tom Lane t...@sss.pgh.pa.us:
Pavel Stehule pavel.steh...@gmail.com writes:
here is rebased patch.
It contains both patches - row_to_array function and foreach array
support.
While I don't have
On Mon, Mar 30, 2015 at 8:11 PM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Mar 27, 2015 at 2:34 AM, Amit Kapila amit.kapil...@gmail.com
wrote:
The reason of this problem is that above tab-completion is executing
query [1] which contains subplan for the funnel node and currently
we
On Mon, Mar 30, 2015 at 8:14 PM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
On Mon, Mar 30, 2015 at 7:41 PM, Jim Nasby jim.na...@bluetreble.com
wrote:
On 3/27/15 2:23 PM, Fabrízio de Royes Mello wrote:
Hi all,
I'm tweaking some autovacuum settings in a table with high
On Mon, Mar 30, 2015 at 4:34 AM, Pavel Stehule pavel.steh...@gmail.com wrote:
Hi
I checked this patch. I like the functionality and behave.
Thanks for the review.
Here I attached updated patch with the following changes.
1. Addition of two new keyword columns
keyword_databases - The
On 03/30/2015 06:46 PM, Stephen Frost wrote:
* Heikki Linnakangas (hlinn...@iki.fi) wrote:
* With CREATE USER PASSWORD 'foo', which hashes/verifiers should
be generated by default? We currently have a boolean
password_encryption setting for that. Needs to be a list.
This generally sounds good
On 03/30/2015 07:20 PM, Peter Geoghegan wrote:
* I think we should decouple the insertion and wal logging more. I think
the promise tuple insertion should be different from the final
insertion of the actual tuple. For one it seems cleaner to me, for
another it will avoid the uglyness
On 03/31/2015 05:25 AM, Petr Jelinek wrote:
Hi,
While reading the code I noticed couple of double semicolons at the end
of lines so I searched for all of them and replaced them with single
ones. The resulting diff is attached.
Thanks, fixed. I also backpatched this, to avoid spurious merge
On 2/12/15 7:28 AM, Jan Urbański wrote:
* If there's already callbacks set: Remember that fact and don't
overwrite. In the next major version: warn.
So yeah, that was my initial approach - check if callbacks are set, don't
do
the dance if they are. It felt like a crutch, though, and racy
Hello,
At Tue, 31 Mar 2015 16:48:18 -0400, Tom Lane t...@sss.pgh.pa.us wrote in
26969.1427834...@sss.pgh.pa.us
Hmm. We can ignore pg_attribute and pg_pltemplate, which don't have OIDs
and thus aren't candidates anyway. And we can ignore the ones
corresponding to the already-existing regFOO
Following on from this -bugs post:
http://www.postgresql.org/message-id/camsr+ygj50tvtvk4dbp66gajeoc0kap6kxfehaom+neqmhv...@mail.gmail.com
this patch adds support for views, foreign tables, and materialised views
to the pg_restore -t flag.
--
Craig Ringer
Jacobo,
* Jacobo Vazquez (jvazq...@denodo.com) wrote:
Am I misunderstanding something or is this the expected behavior? This
not means a replay attack risk? I think that if SSL is not used by the
connection, a malicious user could capture the authentication package which
the client service
On Wed, Apr 1, 2015 at 2:18 AM, Jeff Janes jeff.ja...@gmail.com wrote:
On Tue, Mar 31, 2015 at 1:28 AM, Kyotaro HORIGUCHI
horiguchi.kyot...@lab.ntt.co.jp wrote:
Hi, this is a bug in the commit 0d831389749a3baaced7b984205b9894a82444b9 .
It allows vucuum freeze to be skipped and inversely
Hi,
On 2015-03-30 21:50:09 +0200, Andres Freund wrote:
I'm too fried from the redeye back from pgconf nyc to do anything
complicated, but it seems quite possible to define int64/uint64 based
the stdint.h types if available. And generally a good idea too. I guess
I'll try that tomorrow; unless
On Wed, Mar 25, 2015 at 09:12:41AM -0400, Bruce Momjian wrote:
On Wed, Mar 25, 2015 at 09:37:08PM +0900, Michael Paquier wrote:
On Wed, Mar 25, 2015 at 4:59 PM, Bruce Momjian br...@momjian.us wrote:
On Wed, Mar 25, 2015 at 02:18:58PM +0900, Michael Paquier wrote:
On Fri, Mar 20, 2015 at 07:00:59PM -0400, Robert Haas wrote:
On Fri, Mar 20, 2015 at 6:19 PM, Bruce Momjian br...@momjian.us wrote:
I have not re-ordered the shutdown method options because I am trying to
keep the list logical, from least to most severe, so smart is still
listed first. It
On Tue, Mar 31, 2015 at 2:26 PM, Peter Geoghegan p...@heroku.com wrote:
Andres' wish to do things that way is at least partially motivated by
having logical decoding just work.
I should add that there appears to be some need to terminate the loop
of speculative token waiting. By that I mean
Good point. Next patch attached.
/*
- * Note: we'll reject zero or negative year values. Perhaps negatives
- * should be allowed to represent BC years?
+ * Note: Non-positive years are taken to be BCE.
*/
Previously, zero was rejected, what does it do now? I'm sure it represents
0
The key word you're misunderstanding is filled. It means it doesn't wait
for the 16MB file to be completely filled with records. I.e. what would
happen in the file shipping form of replication.
On Tue, Mar 31, 2015 at 10:34:45AM -0400, Adam Brightwell wrote:
Good point. Next patch attached.
/*
- * Note: we'll reject zero or negative year values. Perhaps negatives
- * should be allowed to represent BC years?
+ * Note: Non-positive years are taken to be BCE.
*/
On Tue, Mar 31, 2015 at 01:17:03PM -0400, Robert Haas wrote:
On Tue, Mar 31, 2015 at 9:11 AM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
Attached a very WIP patch to reduce lock level when setting autovacuum
reloptions in ALTER TABLE .. SET ( .. ) statement.
I think the first
On Wed, Apr 1, 2015 at 2:26 AM, Jeff Janes jeff.ja...@gmail.com wrote:
Did it tell you why? If it surrendered the lock to a competing process,
it should report that as previous INFO messages. If it doesn't give one of
those, then it probably just thinks there are some tuples it can't remove
On 2015-03-31 12:10:48 -0400, Tom Lane wrote:
Andres Freund and...@anarazel.de writes:
On 2015-03-30 21:50:09 +0200, Andres Freund wrote:
I'm too fried from the redeye back from pgconf nyc to do anything
complicated, but it seems quite possible to define int64/uint64 based
the stdint.h
On 31 March 2015 at 16:35, Bruce Momjian br...@momjian.us wrote:
On Wed, Mar 25, 2015 at 09:12:41AM -0400, Bruce Momjian wrote:
On Wed, Mar 25, 2015 at 09:37:08PM +0900, Michael Paquier wrote:
On Wed, Mar 25, 2015 at 4:59 PM, Bruce Momjian br...@momjian.us
wrote:
On Wed, Mar 25, 2015
Andres Freund and...@anarazel.de writes:
On 2015-03-30 21:50:09 +0200, Andres Freund wrote:
I'm too fried from the redeye back from pgconf nyc to do anything
complicated, but it seems quite possible to define int64/uint64 based
the stdint.h types if available. And generally a good idea too. I
On Fri, Mar 20, 2015 at 10:59:41PM -0400, Bruce Momjian wrote:
On Thu, Dec 11, 2014 at 08:35:43PM -0500, Peter Eisentraut wrote:
On 12/11/14 11:44 AM, Kevin Grittner wrote:
We want to finish with VACUUM FREEZE without the FULL, unless we
don't care about missing visibility maps and free
Hi all,
I installed PostgreSQL 9.3 on a Windows Server 2012 and I have
configured it to use SSPI authentication. The client is on a Windows 7
machine and make the connections via ODBC using a DSN with psqlodbc driver
version 9.03.04.00. Authentication works in this scenario for the user
David Fetter da...@fetter.org writes:
On Tue, Mar 31, 2015 at 10:34:45AM -0400, Adam Brightwell wrote:
Previously, zero was rejected, what does it do now? I'm sure it represents
0 AD/CE, however, is that important enough to note given that it was not
allowed previously?
Now, it's supposed to
Peter Eisentraut pete...@gmx.net writes:
With clang -fsanitize=undefined (clang-3.4), I get the following test failure
in ecpg
(it's the only one in the entire tree):
Hm. I don't know why you can't reproduce that in the backend, because
when stepping through DecodeDateTime() on the input
On 03/29/2015 02:55 PM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
I have just claimed this as committer in the CF, but on reviewing the
emails it looks like there is disagreement about the need for it at all,
especially from Tom and Robert.
I confess I have often wanted
Hi all,
attached is v4 of the patch implementing adaptive ndistinct estimator.
I've been looking into the strange estimates, mentioned on 2014/12/07:
values currentadaptive
--
106 99 107
1068 6449190
Robert Haas robertmh...@gmail.com writes:
On Tue, Mar 31, 2015 at 1:49 PM, Joshua D. Drake j...@commandprompt.com
wrote:
Perhaps we could consider it after a year or two, once 9.4 is indeed
very stable, but at that point you have to wonder if it's really worth
the trouble anymore. If someone
With clang -fsanitize=undefined (clang-3.4), I get the following test failure
in ecpg
(it's the only one in the entire tree):
--- a/src/interfaces/ecpg/test/expected/pgtypeslib-dt_test2.stderr
+++ b/src/interfaces/ecpg/test/results/pgtypeslib-dt_test2.stderr
@@ -1,2 +1,4 @@
[NO_PID]: ECPGdebug:
Michael Paquier michael.paqu...@gmail.com writes:
On Tue, Mar 31, 2015 at 9:40 AM, Peter Eisentraut pete...@gmx.net wrote:
I'm interested in the exact syntax you'd use, to compare it to the
currently used techniques.
With the presence of VERSION_NUM directly in pg_config, the following
On Tue, Mar 31, 2015 at 12:58:27PM -0400, Tom Lane wrote:
David Fetter da...@fetter.org writes:
On Tue, Mar 31, 2015 at 10:34:45AM -0400, Adam Brightwell wrote:
Previously, zero was rejected, what does it do now? I'm sure it
represents 0 AD/CE, however, is that important enough to note
Kyotaro HORIGUCHI horiguchi.kyot...@lab.ntt.co.jp writes:
If I'm not missing anyting, putting stereotyped information about
GUC contexts like following would be usable.
share_buffers (integer), (effective after server restart)
log_destination (string), (effetive after config reload)
On Tue, Mar 31, 2015 at 9:11 AM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
Attached a very WIP patch to reduce lock level when setting autovacuum
reloptions in ALTER TABLE .. SET ( .. ) statement.
I think the first thing we need to here is analyze all of the options
and determine
On 03/31/2015 10:58 AM, Robert Haas wrote:
On Tue, Mar 31, 2015 at 1:49 PM, Joshua D. Drake j...@commandprompt.com wrote:
Perhaps we could consider it after a year or two, once 9.4 is indeed
very stable, but at that point you have to wonder if it's really worth
the trouble anymore. If someone
On Tue, Mar 31, 2015 at 1:28 AM, Kyotaro HORIGUCHI
horiguchi.kyot...@lab.ntt.co.jp wrote:
Hi, this is a bug in the commit 0d831389749a3baaced7b984205b9894a82444b9 .
It allows vucuum freeze to be skipped and inversely lets regular
vacuum wait for lock. The attched patch fixes it.
In
On 03/31/2015 10:51 AM, Andres Freund wrote:
On 2015-03-31 10:49:06 -0700, Joshua D. Drake wrote:
On 03/31/2015 04:20 AM, Heikki Linnakangas wrote:
Perhaps we could consider it after a year or two, once 9.4 is indeed
very stable, but at that point you have to wonder if it's really worth
the
On 03/31/2015 04:20 AM, Heikki Linnakangas wrote:
I believe that Heikki said he'd backpatch that when 9.4 was considered
very stable. I don't think that we've reached that level of confidence
in the invasive B-Tree bugfixes that went into 9.4 yet.
I have no intention to backpatch the
On 03/31/2015 04:20 AM, Heikki Linnakangas wrote:
On 03/30/2015 09:57 PM, Peter Geoghegan wrote:
On Mon, Mar 30, 2015 at 7:50 PM, Joshua D. Drake
j...@commandprompt.com wrote:
We have a database that has run into this problem. The version is
9.1.15 on
Linux. I note in this thread:
On 03/31/2015 11:05 AM, Josh Berkus wrote:
I have no intention to backpatch the changes. Too big, too invasive.
Perhaps we could consider it after a year or two, once 9.4 is indeed
very stable, but at that point you have to wonder if it's really worth
the trouble anymore. If someone has runs
On Tue, Mar 31, 2015 at 1:29 AM, Michael Paquier michael.paqu...@gmail.com
wrote:
On Tue, Mar 31, 2015 at 3:42 PM, Jeff Janes jeff.ja...@gmail.com wrote:
On Mon, Mar 30, 2015 at 8:54 PM, Jeff Janes jeff.ja...@gmail.com wrote:
After freeing up the rows at the end of the table so it is
Hi.
I'm just posting this WIP patch where I've renamed fastbloat to
pgstatbloat as suggested by Tomas, and added in the documentation, and
so on. I still have to incorporate Amit's comments about the estimation
of reltuples according to the way vacuum does it, and I expect to post
that tomorrow
On 2015-03-31 10:49:06 -0700, Joshua D. Drake wrote:
On 03/31/2015 04:20 AM, Heikki Linnakangas wrote:
Perhaps we could consider it after a year or two, once 9.4 is indeed
very stable, but at that point you have to wonder if it's really worth
the trouble anymore. If someone has runs into that
On Tue, Mar 31, 2015 at 1:49 PM, Joshua D. Drake j...@commandprompt.com wrote:
Perhaps we could consider it after a year or two, once 9.4 is indeed
very stable, but at that point you have to wonder if it's really worth
the trouble anymore. If someone has runs into that issue frequently, he
Jim Nasby jim.na...@bluetreble.com wrote:
On 3/27/15 5:15 AM, Vladimir Borodin wrote:
Master writes this record to xlog in btvacuumscan function after
vacuuming of all index pages. And in case of no pages with
deleted items xlog record would contain lastBlockVacuumed 0.
In btree_xlog_vacuum
On Tue, Mar 31, 2015 at 05:25:48PM +0100, Thom Brown wrote:
Slightly updated patch attached and applied. I moved asciidoc after
HTML in the list, rather than at the end. Thanks for everyone's hard
work on this.
I think I done gone broke it:
CREATE TABLE | 3^.||moo|hello,
On 03/30/2015 09:01 PM, Jeff Janes wrote:
commit 2c03216d831160bedd72d45f7 has invalidated the part of the docs
saying If no WAL has been written since the previous checkpoint, new
checkpoints will be skipped even if checkpoint_timeout has passed,
presumably by accident.
It seems that this part
On Tue, Mar 31, 2015 at 1:09 PM, Heikki Linnakangas hlinn...@iki.fi wrote:
I'm pretty sceptical of that. ISTM you'll need to do modify the page twice
for each insertion, first to insert the promise tuple, and then to turn the
promise tuple into a real tuple. And WAL-log both updates. That's
Heikki,
* Heikki Linnakangas (hlinn...@iki.fi) wrote:
On 03/30/2015 06:46 PM, Stephen Frost wrote:
Unfortunately, the first major release with this will certainly need to
default to including md5 as we can't have a password update or change
break clients right off the bat. What I think would
On 3/31/15 1:05 AM, Michael Paquier wrote:
On Tue, Mar 31, 2015 at 9:40 AM, Peter Eisentraut pete...@gmx.net
mailto:pete...@gmx.net wrote:
On 3/30/15 6:29 PM, Michael Paquier wrote:
On Tue, Mar 31, 2015 at 5:39 AM, Peter Eisentraut pete...@gmx.net
On Wed, Apr 1, 2015 at 8:50 AM, Peter Eisentraut pete...@gmx.net wrote:
On 3/31/15 1:05 AM, Michael Paquier wrote:
On Tue, Mar 31, 2015 at 9:40 AM, Peter Eisentraut pete...@gmx.net
mailto:pete...@gmx.net wrote:
On 3/30/15 6:29 PM, Michael Paquier wrote:
On
On Wed, Apr 1, 2015 at 4:09 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Michael Paquier michael.paqu...@gmail.com writes:
On Tue, Mar 31, 2015 at 9:40 AM, Peter Eisentraut pete...@gmx.net
wrote:
I'm interested in the exact syntax you'd use, to compare it to the
currently used techniques.
Hi,
The pg_amproc functions for inet_gist were accidentally added under the
gin heading. I have attached a patch which moves them to the gist
heading where they belong.
--
Andreas Karlsson
diff --git a/src/include/catalog/pg_amproc.h b/src/include/catalog/pg_amproc.h
index 8a43f64..78c3bd9
Andrew Dunstan and...@dunslane.net writes:
On 03/29/2015 02:55 PM, Tom Lane wrote:
It may be that these two cases are so much more useful than any other
conceivable cases that we can do them and stop, but I don't think that
argument has been made convincingly.
Well, here's a list of all the
Observe these recent buildfarm failures:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=muledt=2015-03-21%2000%3A30%3A02
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=guaibasaurusdt=2015-03-23%2004%3A17%3A01
65 matches
Mail list logo
