for user groups is listed in several places. But it fails to load a
web page.
http://pugs.postgresql.org/
I tried two browsers several times. Other pages at:
http://www.postgresql.org/
work well for me.
It is currently working for me.
--
Robert Haas
EnterpriseDB: http
to report this to the Ubuntu folks.
--
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 install with administrator account. No differernce.
However, there is no such bug with v9.0.6.
Hmm, maybe initdb is hanging? Is there an installer log someplace,
perhaps in your temp directory?
Could you run:
initdb -d -D some_pathname
...and capture the output?
--
Robert Haas
EnterpriseDB
, and OTHERS is not an exception name, just a
PL/pgsql construct. Maybe we could work a cross-reference into the
sentence that mentions PL/plgsql, though.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
for checkpoint activity).
Hmm, so what should we adjust it *to*?
--
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
the relevant difference might be. The
debugger plugin *might* be relevant, but I think it's more likely a
red herring, and the real issue is something else entirely.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list
files, although Tom Lane, a PostgreSQL core team member, also
works at Red Hat. I would suggest that you take this up with Red Hat
directly...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
think you need a -c in there somewhere, maybe something like this:
options='-cclient_encoding=WIN1250'
...although, for some reason, I can't get that to work from psql, even
though I can set other parameters using that syntax.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
uniquely identify a point in time, even if you know
what time zone it's relative to. That combination of years, minutes,
days, hours, minutes, and seconds can occur twice, if it's near a DST
boundary.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent
that are hard to find and perhaps
dependent on the exact compiler version used.
But I'm completely cool with doing this for platforms where we haven't
otherwise got an implementation. Any port in a storm.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
exactly you did. If
you come up with a specific sequence of steps involving simple tools
like pg_dump and psql that produces a result you think is wrong,
someone here can probably (a) tell you whether the behavior is
intended, and (b) if not, fix it.
--
Robert Haas
EnterpriseDB: http
the servers plz tell me and i will post
them.any information that you may have is more than welcome. thx in advance
Could you send the output of pg_controldata on the standby, and also
the contents of pg_clog on that machine?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
, if you
want more advice on this topic, I suggest posting to a more
appropriate mailing list with specific details of the problem you are
having.
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
documenting, fixing, or adding this to the TODO list?
At most I would say we could try to improve the error message.
--
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
On Wed, Nov 23, 2011 at 7:19 AM, Peter Geoghegan pe...@2ndquadrant.com wrote:
On 23 November 2011 02:49, Robert Haas robertmh...@gmail.com wrote:
There is no sort of systematic labeling of error messages in the log
to enable the DBA to figure out that the first error message is likely
nothing
a workaround for our failure to classify things properly.
--
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
place:
http://postgis.refractions.net/mailman/listinfo/postgis-users
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Tue, Nov 15, 2011 at 5:16 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
NEW used to be a reserved keyword, but it's not so in 9.0 anymore. So 9.0
pg_dump thinks it doesn't need to be quoted.
Why isn't it correct?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
for everyone, so can you give us
some clues about what might be different in your environment?
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
to sit down in front of the computer and
poke at it a bit seems likely to get you the results you are looking
for quite a bit more quickly.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
-format email, it
would make it easier to help people.
The symptoms that you are describing sound pretty odd to me.
PostgreSQL is a database, not a piece of malware. How exactly did you
install it in the first place?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
.
--
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
installers anyway;
you used something provided by Holdem Manager, and I think you need to
complain to them, not us.
--
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
On Fri, Nov 4, 2011 at 1:21 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Nov 3, 2011 at 5:07 PM, Tom Lane t...@sss.pgh.pa.us wrote:
We probably ought to have something in there to throw an error ...
Probably not for rules in general, but we
, there's always auto_explain, but
that has some overhead and is a bit more work to set up.
--
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
the actual value ( possibly changed by ALTER TABLE
... ).
Maybe I just need more caffeine, but I don't see what the problem is?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
a second branch to the index condition to stop the scan,
just as we already do for:
EXPLAIN (ANALYZE, BUFFERS) select * from test where value0.9993 and
value 0.;
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql
On Mon, Oct 31, 2011 at 10:37 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Sun, Oct 30, 2011 at 11:39 PM, Maksym Boguk maxim.bo...@gmail.com wrote:
Seems index scan cannot stop after finding first NULL during scan on ''
condition, and doing scan through
of the software in a
non-standard fashion, so it's really impossible for us to give any
useful advice.
--
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
: quoting needed for column name with non ascii chars
Details:
I run sql from pg-admin:
create table a(straßße int)
On windows this creates a column which has empty name. However, it works
well on Linux and Mac.
What happens if you run the same command from psql?
--
Robert Haas
for it.
I think my vote would be to just fix it in master.
--
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
of that, this is small potatoes by
comparison.)
--
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
not believe, because it
means more code to maintain and frequently confuses users to no
benefit) but rather that this particular configuration option is
needed to support some sensible use case that can't be supported any
other way.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
as
incorrect.
Thanks for the support and replies on my work.
I would be curious to see (updated, corrected) results on older versions.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
should just patch the
docs. 9.1 hasn't been out for very long, so maybe expectations aren't
too settled yet, but changing security-critical behavior in back
branches doesn't seem like a wonderful idea; and I think I mildly
prefer the current semantics to the proposed ones.
--
Robert Haas
be broken on Windows, and I think someone would have noticed that by
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
doesnot work with bytea
Details:
To persist a blob you can also use bytea. Unfortunately the JDBC driver does
not support this.
I think you'll need to raise this issue on the pgsql-jdbc mailing
list, as this list is only for bugs in the core distribution.
--
Robert Haas
EnterpriseDB: http
--
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
need any more information.
-David Baumgold
Do you have config.log?
--
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
be a windows
issue rather than a postgre bug, but I thought I'd ask for help anyway.
Thank you in advance for any advice.
I think this is one of the known issues with the 8.2 installer.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs
it is a oid type.
Any suggestion?
Thanks
I haven't seen any replies to this; you might want to try on the
pgsql-odbc mailing list, as this list is for bugs in the core
distribution.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql
about 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
clear to me what the issue is. Is
there some confusion between the encoding of the file and the encoding
in use in the client session? It's odd that we would have a bug that
only affects win1252.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent
to that directory? Did
the installer leave behind a log file anywhere?
--
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
On Fri, Oct 14, 2011 at 12:29 AM, Vishnu S. vishn...@nestgroup.net wrote:
The application deletes the contents of tables in the tablespace using
DELETE TABLE query.
There's no DELETE TABLE command. Do you mean DELETE, or DROP TABLE?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
.
Thanks, committed.
--
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
would help a lot. Just off the top
of my head, a likely culprit is that you may need to adjust your
pg_hba.conf file.
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
://jira.freeswitch.org/secure/attachment/14751/odbc.txt
This mailing list is for PostgreSQL bugs. We don't maintain unixODBC.
--
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
the MSVC build system.
--
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
is in some particular
format, rather than just whatever the input function will accept...
--
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 Thu, Sep 29, 2011 at 7:23 AM, Yaamini Bist yaamini.b...@ericsson.comwrote:
Hi,
It would be really great if you can provide me information *Is PostGre
compatible to RHEL 6.1 ?*
1. Yes.
2. This is not a bug.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
On Mon, Sep 26, 2011 at 12:45 AM, Ramanujam innomot...@gmail.com wrote:
On Mon, Sep 26, 2011 at 9:57 AM, Robert Haas robertmh...@gmail.com wrote:
Does it work if you use EXECUTE?
Apologies to have not included the list when I replied to Pavel.
Re-writing it as a dynamic sql stmt indeed works
On Mon, Sep 26, 2011 at 11:00 AM, Robert Haas robertmh...@gmail.com wrote:
The whole thing is a bit mysterious because ExecQual() doesn't really
do much that seems like it could generate an invalid memory reference.
I'll poke at this some more...
I added some debugging code which sets
On Mon, Sep 26, 2011 at 11:40 AM, Robert Haas robertmh...@gmail.com wrote:
To check my work, I did this:
--- a/src/backend/executor/execQual.c
+++ b/src/backend/executor/execQual.c
@@ -5003,6 +5003,7 @@ ExecQual(List *qual, ExprContext *econtext, bool
resultForNull)
Datum
unsafe because the planner is
destructive wrt the input tree. for my application, it often causes
a crash in executor.
I was just wondering about that. It seems like it could very well be
the same issue, but I have not tested it yet.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
On Mon, Sep 26, 2011 at 12:20 PM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Sep 26, 2011 at 12:17 PM, Merlin Moncure mmonc...@gmail.com wrote:
hm. any relation to YAMAMOTO Takashi's recent email, [BUGS] bug in
plancache.c, which hasn't hit the archives yet?
GetCachedPlan can pass
On Fri, Sep 23, 2011 at 11:36 PM, YAMAMOTO Takashi
y...@mwd.biglobe.ne.jp wrote:
see the following patch.
it seems some function names in the comment are out of sync with the reality.
Thanks, fixed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
;
Throws an error:
NUM:42P02, DETAILS:there is no parameter $1
Substrituting $1 with parm gives this error:
NUM:42703, DETAILS:column parm does not exist
Does it work if you use EXECUTE?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql
On Sun, Sep 18, 2011 at 5:10 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Sep 15, 2011 at 12:05 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
Excerpts from Abel Abraham Camarillo Ojeda's message of mié sep 14 18:33:33
-0300 2011:
_n_srv
On Wed, Sep 21, 2011 at 11:35 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Sun, Sep 18, 2011 at 5:10 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Sep 15, 2011 at 12:05 AM, Tom Lane t...@sss.pgh.pa.us wrote:
In that case I'm betting Robert broke
.
--
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
But in this case I think you're likely to still need a cast in there 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
;
DROP TABLE
_n_srv=# create table pg_temp.c (x int unique);
ERROR: temporary tables cannot specify a schema name
FWIW this does work in 9.0.
In that case I'm betting Robert broke it somewhere in the unlogged-table
changes.
Yeah, looks like it. Will investigate.
--
Robert Haas
.
--
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
have to patch the following regex:
^([a-zA-Z]:)\\([0-9a-zA-Z_\\\s\.\-\(\)]*)$
Sorry for the inconvenience. :-(
--
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
On Tue, Sep 13, 2011 at 4:31 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Sep 10, 2011, at 11:26 PM, Tom Lane t...@sss.pgh.pa.us wrote:
(IOW, rather than fix this I'd prefer to rip out the code altogether.
But maybe we should wait a couple more years
... but if nobody feels motivated to go do
that, doing at least this much would remove the foot-gun. So +1 for
that.
--
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
On Sep 10, 2011, at 11:26 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Thom Brown t...@linux.com writes:
I don't use rules, but in a bit of experimentation on Git master, I
discovered the following behaviour:
CREATE TABLE test1 (id serial primary key, things text);
CREATE TABLE test2 (id serial
of now-unneeded segments) to take priority over
getting new ones.
--
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
. Robert?
Yeah, sorry about that. I really booted that one, but it was fixed
July 21st on REL9_1_STABLE.
--
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
/Guide_to_reporting_problems
--
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 Wed, Jul 20, 2011 at 8:24 AM, Renzo Kottmann rkott...@mpi-bremen.de wrote:
On 07/18/2011 05:25 PM, Robert Haas wrote:
On Tue, Jul 12, 2011 at 9:18 AM, Sandro Santilli s...@keybit.net wrote:
Trying to exclude items from dumps of postgis-enabled databases
we use pg_restore -l output and strip
question here:
http://archives.postgresql.org/pgadmin-support/
This list is only for bugs in PostgreSQL itself, and not all of the
pgAdmin developers read it regularly.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list
.
--
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
comparisons. Note that:
IF (something_that_is_null) THEN
...
END IF;
...will not trigger the if, and:
IF (something_that_is_null = false) THEN
...
END IF;
won't either.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list
/lib/libxml2.so.
Any idea what query triggered 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
not installing the
adminpack.
This is really an issue for one of the pgadmin mailing lists, not so
much here...
--
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
to read this:
http://wiki.postgresql.org/wiki/Submitting_a_Patch
And add your patch here:
https://commitfest.postgresql.org/action/commitfest_view/open
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
, I agree with you that the behavior here leaves a lot to
be desired. Hunting down the privilege grant that is stopping you
from dropping a user is pretty darn annoying. I am not sure what to
do about that, though.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL
f3ff0433ab32fdc69da3c8f8e691ef6b4366559c on July 14th.
--
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
,
ii, n_ii * sizeof(INTERFACE_INFO),
length, 0, 0)
Perhaps there's a better method we could be using, but I have no idea
what it is. A quick Google search didn't turn up any IPv6-related
restrictions on SIO_GET_INTERFACE_LIST.
--
Robert Haas
this problem.
--
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, Jul 8, 2011 at 5:21 AM, Kyotaro HORIGUCHI
horiguchi.kyot...@oss.ntt.co.jp wrote:
Points to realize this follows,
Please add your patch to the next CommitFest.
https://commitfest.postgresql.org/action/commitfest_view/open
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
from a separate file.
The attached patch seems like an appropriate fix. However, I'm unsure
whether to apply it to released branches ... does anyone think this
might break somebody's application?
I think this is pretty safe.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
back-patch it to 9.1 and 9.0?
(c) Should we consider removing compatibility with the ancient copy
syntax in 9.2, and de-reserving that keyword? (Given that the
workaround is this simple, I'm inclined to say no, but could be
persuaded otherwise.)
--
Robert Haas
EnterpriseDB: http
On Tue, Jul 5, 2011 at 11:30 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Jul 5, 2011 at 11:06 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
I assume it's not in unreserved_keyword because it would cause a
shift/reduce conflict elsewhere
-7.3 syntax is dead in fact for many years.
...this is not something we're going to back-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
functions have any applicability to this problem?
--
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 Tue, Jul 5, 2011 at 12:42 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Sun, Jul 3, 2011 at 12:31 PM, Tom Lane t...@sss.pgh.pa.us wrote:
The code that recognizes a default expression as being just constant
NULL doesn't think this is a constant NULL
in adavance
Data from older versions of PostgreSQL can generally be restored to
newer versions just fine. But it's not really clear what problem you
are having here, so it's hard to provide any more help than that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
setting for this, if it's affecting a lot
of people.
--
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
2011/6/16 Luiz K. Matsumura l...@planit.com.br:
Em 16/06/2011 16:39, Robert Haas escreveu:
2011/6/10 Luiz K. Matsumura l...@planit.com.br:
I need help to know if the follow scenario is a expected behaviour, a bug of
postgres or a bug of slony:
Postgres v8.4.8
Slony-I v 2.0.5
I have
in
a trigger of a replicated table ?
I'm confused. If you enable the trigger on table2, it's going to fire
when someone updates table2. Whether or not the update is coming from
another trigger or directly from the user has nothing to do with it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
WHERE t1_id = 1;
--1
When you use a foreign key with inheritance, only the rows that are
actually in the parent table itself are considered for purposes of the
foreign key.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing
it in beta2.
--
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
client with the same pSQLODBC 9.03 but 32 bits works fine.
I haven't seen a reply to this bug report; you may want to try the
psql-odbc mailing list.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
compile with #include wumpus.h).
But it doesn't.
--
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
: REL-1-12-2
You might want to ask about this on pgadmin-support. I'm guessing
there is an encoding setting wrong somewhere, but as a non-user of
pgAdmin I'm not sure where to look for it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
technically no longer part
of the standard.
It's still extremely widely used though, I think, and very useful. I
don't feel we have to support GROUP BY 1 COLLATE whatever, but it
might be worth the trouble to at least emit a decent HINT.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
101 - 200 of 731 matches
Mail list logo
