a
brief history of how I ended up where I am.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Fri, Jun 3, 2011 at 2:21 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jun 3, 2011 at 1:19 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Now, if the query doesn't involve any explicit reference to joinalias.*,
we could probably fake it with some ugly
On Tue, Jun 7, 2011 at 11:50 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Patch along these lines attached.
Frankly, I find this quite ugly, and much prefer the general approach of
your previous patch in banlktim433vf5hwjbj0fswm_-xa8dda...@mail.gmail.com
On Tue, Jun 7, 2011 at 11:41 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
If your point here is that you don't want to spend time hacking on
this because it's a fairly marginal feature and therefore not terribly
high on your priority list, I can understand
On Tue, Jun 7, 2011 at 2:05 PM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Jun 7, 2011 at 11:50 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Patch along these lines attached.
Frankly, I find this quite ugly, and much prefer the general approach
On Tue, Jun 7, 2011 at 3:53 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I found a few other holes in my previous patch as well. I think this
plugs them all, but it's hard to be sure there aren't any other calls
to RelationGetNumberOfBlocks() that could
On Tue, Jun 7, 2011 at 5:05 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Jun 7, 2011 at 3:53 PM, Tom Lane t...@sss.pgh.pa.us wrote:
It might be that it'd be best just to have both the planner and executor
throwing errors on unlogged tables, rather
On Tue, Jun 7, 2011 at 6:06 PM, Robert Haas robertmh...@gmail.com wrote:
But for the planner, why not just put the same kind of test in
get_relation_info, just after it does heap_open?
OK, let me try that.
Seems to work beautifully, so committed that way.
--
Robert Haas
EnterpriseDB: http
On Fri, Jun 3, 2011 at 1:01 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Robert Haas's message of vie jun 03 12:44:45 -0400 2011:
On Wed, Jun 1, 2011 at 2:28 PM, Robert Haas robertmh...@gmail.com wrote:
(4) It strikes me that it might be possible to address this problem
On Wed, Jun 1, 2011 at 2:28 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, May 26, 2011 at 12:34 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
Excerpts from Euler Taveira de Oliveira's message of jue may 26 12:00:05
-0400 2011:
I think we
is to avoid USING: it wasn't one of the SQL
committee's better ideas.
I don't understand why we can't just translate the USING into some
equivalent construct that doesn't involve USING. I proposed that a
while ago and you shot it down, but I didn't find the reasoning very
compelling.
--
Robert Haas
On Fri, Jun 3, 2011 at 1:19 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jun 3, 2011 at 10:59 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Personally my advice is to avoid USING: it wasn't one of the SQL
committee's better ideas.
I don't understand why
On Wed, May 25, 2011 at 7:29 AM, Susanne Ebrecht
susa...@2ndquadrant.com wrote:
I think we should fix the documentation here.
Patch?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
is
almost certainly gone in more recent versions. It would be nice to
track done and fix whatever is wrong in the older branches, but we'd
probably need a reproducible test case of some sort. I don't think it
craps out like that EVERY time you interrupt it...
--
Robert Haas
EnterpriseDB: http
On Wed, Jun 1, 2011 at 1:15 PM, Robert Haas robertmh...@gmail.com wrote:
2011/5/31 Andres Freund and...@anarazel.de:
On Tuesday, May 31, 2011 03:27:22 Alvaro Herrera wrote:
Excerpts from Andres Freund's message of lun may 30 20:47:49 -0400 2011:
On Tuesday, May 31, 2011 02:35:58 AM Andres
disinclined to put in the
time to fix this.
However, patches are welcome...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
patch...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
that's a 9.2 project.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
to fix this.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
locale-aware
functions on Windows, or just different ones, but I wouldn't even know
where to start looking for that sort of problem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
reject-unlogged-during-recovery.patch
Description: Binary data
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
I
think the current default is good, because it means you only need to
change ONE parameter to switch from async rep to sync rep (namely,
synchronous_standby_names).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list
they're doing), and
to get stack traces of where they are stuck using gdb.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
and the integrity of your hardware.
This kind of thing usually means that corruption is happening somewhere, and
if you don't track it down and fix it, eventually it will probably add up to
something serious.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Sun, May 15, 2011 at 5:02 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, May 12, 2011 at 6:20 PM, Tom Lane t...@sss.pgh.pa.us wrote:
One possibility is to start showing default when the ACL is null,
which would be quite easy to implement
anyone feel this is worth changing? I am concerned such a change
would break many user applications.
The backward compatibility problem is pretty icky, but I don't much
like the idea of leaving it as-is, either.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL
://archives.postgresql.org/
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
'), 'default')
But that might be too big a change.
I don't think that's too big a change. ISTM we ought to change
something. Another idea would be to always show the permissions, even
if nothing has been changed from the defaults.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
, test
recursive trigger calls). Although Ill admit, given the point we are
in the release I could see a revert also being justified.
Greg, big thanks for testing! keep it up! :)
Do we need to apply this patch?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL
. Could someone
reproduce this and get a stack trace?
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
Based on Tom's recent commits, this might now be fixed in the latest sources.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
or
remove any of your data. Improving things so that sysctl.conf is less
likely to require alteration is on our radar screen, but changing that
file is not normally a dangerous operation. I am not sure what went
wrong for you.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
does not shut down
You may want to try shutting down with -m fast. Without that, it
waits for all clients to disconnect before shutting down, and
sometimes clients don't do that quickly, or at all.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
/postgresql/8.4/bin/pg_ctl?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
\lo_import instead.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
virtualization tool you are using.
Any way to get a stack trace on the assertion failure?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
for instructions on what to put in there, or here:
http://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
sessions while leaving a
transaction open. Presumably each client should commit after it
finishes its own work.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
2e82d0b396473b595a30f68b37b8dfd41c37dff8 have possibly fixed this?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
-obvious aspect of your configuration. The EnterpriseDB team has
made multiple attempts to reproduce this internally, and while we've
managed to create various weird behaviors, they aren't obviously the
same as what's happening to you. :-(
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
suggestions?
If you haven't already, you might want to try this question on the
pgadmin-support mailing list.
http://archives.postgresql.org/pgadmin-support/
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
anywhere(server or client).
My guess is that, depending on how you connect, something in your
environment is different, and that is what is making the Oracle
connection succeed or fail.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs
information leak.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
'.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
, then it would be helpful if
you could attempt to obtain a stack backtrace.
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing
On Mon, Apr 25, 2011 at 11:06 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Apr 20, 2011 at 7:13 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I have stated previously my opinion that this is a misconceived feature,
and it's now apparent
a C funcion: elog(FATAL, Terminating connection...);)
then no.
A smart shutdown waits for clients to exit on their own. A fast or
immediate shutdown kills them immediately, even mid-query.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
bouncing out from under us, so if we release it, aren't we potentially
point off into thin air?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
On Tue, Apr 5, 2011 at 11:18 AM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Robert Haas robertmh...@gmail.com wrote:
This patch looks reasonable, but I'm a bit concerned about the
chunk immediately preceding the patched area.
When we do this:
LWLockRelease
to
work on MacOS X, but I don't have a mingw environment handy.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
disable-shared.patch
Description: Binary data
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
On Tue, Apr 5, 2011 at 12:13 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
I wrote:
Robert Haas robertmh...@gmail.com wrote:
If you could send a revised patch, that would be great.
Attached. I put it in the same spot relative to the lock
acquisition that was used earlier
On Mon, Mar 28, 2011 at 12:29 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I think we've had a number of pieces of evidence that suggest that
extending 8kB at a time is too costly, but I agree with Greg that the
idea of extending an arbitrarily large table
contiguously on disk. But I'd want to see some careful
testing that reveals exactly what is needed to get that benefit before
we go too crazy with it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
, in this case, we could
cache the table size, or the fact that vacuum has just truncated away
N blocks, or, uh, something. *waves hands* But it's hard to know how
such an area could reasonably be sized or managed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL
to
try and understand why configure does not see these libraries.
Maybe you have the readline and zlib packages installed, but not
readline-devel and zlib-devel? That's usually what bites me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
in a surprising way.
.pgpass files are explicitly put there by a user, so they know what
they've done.
Putting a password in cleartext somewhere is an issue if people don't
know about it.
I agree completely.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
this form:
http://www.postgresql.org/community/lists/subscribe
and selecting pgsql-general list.
Or better yet, contact Poker Tracker, since this doesn't actually
appear to be a question about PostgreSQL.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
command. You may want to update it in
postgresql.conf (and then reload the config using pg_ctl reload). Or
you could use ALTER ROLE .. SET or ALTER DATABASE .. SET, if you don't
want to change it globally.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Fri, Mar 11, 2011 at 9:31 AM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Thu, Mar 10, 2011 at 10:37 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Thu, Mar 10, 2011 at 4:08 PM, Bruce Momjian br...@momjian.us wrote:
Was this fixed?
Not yet. ?I can
On Thu, Mar 10, 2011 at 10:37 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Thu, Mar 10, 2011 at 4:08 PM, Bruce Momjian br...@momjian.us wrote:
Was this fixed?
Not yet. I can probably fix it, if nobody else wants to do it.
Well, it has languished for five months, so
On Fri, Mar 11, 2011 at 5:56 AM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Tue, Jan 25, 2011 at 10:54 AM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Robert Haas robertmh...@gmail.com wrote:
I think this patch would only be adding to the confusion. ?When
to create more new roles? (y/n)
Sorry for the late reply. If you press enter, no is the default.
That's a lame answer. Surely this is a documentation bug.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
On Fri, Mar 11, 2011 at 10:05 AM, Bruce Momjian br...@momjian.us wrote:
Also, it seems this was addressed in January:
commit af84bee43e356866dc46c95ae5bf77996a8237ff
Author: Robert Haas rh...@postgresql.org
Date: Sat Jan 8 06:12:05 2011 -0500
Remove bogus
: PostgreSQL8.2
Details:
I am getting an error in my PostGreSQL8.2
Error 1053: The service did not respond to the start or control request in a
timely fashion
What do you see in the server log file?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Thu, Mar 10, 2011 at 4:08 PM, Bruce Momjian br...@momjian.us wrote:
Was this fixed?
Not yet. I can probably fix it, if nobody else wants to do it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
changed it to check for language ownership.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
scaling/rotation.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
for 8.3 and 8.4)?
I think a lot of these things are already documented. Aren't they?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
it's a good change, but we should make sure to release-note it
properly, along with the change you made for PLs.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
happened.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
##
configure: WARNING: ## ##
checking for uuid.h... yes
Hmm. What platform is this on? And what's in config.log?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
)?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
from your side.
This isn't a bug. You should try your question on pgsql-general or
pgsql-novice, with a lot more detail.
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs
message report 5433 as default port
Details:
running postgresql-9.0.3-1-windows.exe --help
tells the default port for postgres is 5433
(supposed to be 5432).
I can reproduce this. It appears to be an installer bug. Dave?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
could just call
that function and pass it an SQL query every time you want to do this.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
in that version also..there was the same problem. its there
anyway to solve this problem or reset this password
This report is missing a few key details, such as exactly how you are
trying to connect, and the exact text of whatever error message you
are getting.
--
Robert Haas
EnterpriseDB
this has been fixed. Please let me know if not.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
if one could specify a comma separated list of
databases to skip (e.g. template1, postgres etc.)
Seems like it could be useful, or maybe a list of databases to include
would be better, not sure.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
.
It seems like there are a lot of possible combinations here that could
be useful, so we'd want something that allowed a fairly flexible
specification of what to match.
Is this a problem you're interested in working on (i.e. contributing code)?
--
Robert Haas
EnterpriseDB: http
to explain. It'd be interesting to compare the disk blocks in the
index on the standby with the disk blocks in the index on the master
and figure out which ones are different and in what way. pg_filedump
might be useful.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL
worked as it should. It
was only the usage of the % that failed to work properly while
authenticatin via the ODBC driver.
You may want to try this question on the ODBC list, if you don't get a
response here.
http://archives.postgresql.org/pgsql-odbc/
--
Robert Haas
EnterpriseDB: http
On Sat, Feb 26, 2011 at 2:14 AM, Bruce Momjian br...@momjian.us wrote:
Has this been addressed?
Not me. Sounds like no one cares enough to figure out how to do this.
Perhaps this should be a TODO.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
install PostgreSQL?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
list. You might try here:
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
On Tue, Feb 8, 2011 at 7:23 PM, mark dvlh...@gmail.com wrote:
(~two weeks and it dies)
keepalives_idle=30
keepalives_interval=30
keepalives_count=30
Maybe something like this:
keepalives_idle=60
keepalives_interval=5
keepalives_count=10
--
Robert Haas
EnterpriseDB: http
version.
This list is only for bugs in core PostgreSQL, not PgOleDb. Also,
this sounds like it's more likely to be a configuration problem than a
bug. You'll need to contact whoever is responsible for PgOleDb, or
peruse the appropriate documentation.
--
Robert Haas
EnterpriseDB: http
this, and it's fixed now.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
://archives.postgresql.org/pgsql-es-ayuda/
It'd also probably be helpful to provide more details about the problelm.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription
responses to this bug. Do we have a quoting problem somewhere?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
instead of AccessShareLock to prevent this.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
figure out how to get it working, I think we'd be happy to
accept a patch that fixes it, unless it's only failing due to some
funky detail of your configuration, which I suspect isn't the case
based on a quick look at my system.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
On Thu, Mar 3, 2011 at 11:38 AM, Dave Page dp...@pgadmin.org wrote:
On Thu, Mar 3, 2011 at 8:30 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Feb 2, 2011 at 4:06 PM, R. Engmann rengm...@web.de wrote:
The following bug has been logged online:
Bug reference: 5863
Logged
the problem by
deleting my .pg_history file.
Perhaps it is more accurate that this is a problem with termcap?
More likely libedit, which FWICT seems to be riddled with bugs. :-(
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing
for debugging. Or at least it's never
bothered me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
think this behavior is determined
by the operating system behavior of the locale you've selected, and we
just believe whatever the OS says.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
)
NOTICE: (2,Robert)
NOTICE: (3,Tom)
debug_query
-
(1 row)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
was
typing in a query (not running it), and I had to hard-reboot...now i can't
run the query tool.
You probably need to try the pgadmin-support list:
http://www.pgadmin.org/support/list.php
This list is for bugs in core PostgreSQL.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
, but we already can't do that if there are any
bits set in the visibility map. It could also leave some bloat in
the table, but probably not much (he says hopefully).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list
201 - 300 of 731 matches
Mail list logo
