function.
As I understand you, that should have solved the problem. The result,
however, is exactly the same as before.
You may get further if you post the modified code, instead of simply
asserting that some code we can't see doesn't work.
--
Robert Haas
EnterpriseDB: http
On Fri, Feb 4, 2011 at 10:45 PM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
Is there really a use case for users fiddling with pg_proc, pg_class,
etc. directly?
There's a use case for *superusers* to fiddle with them, yes.
(Superusers
mentioned here:
http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=31b6fc06d83c6de3644c8f2921eb7de0eb92fac3
I believe this requires some refactoring to fix. It would be good to do that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
on Windows...
--
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 the above is certainly a lot better than nothing.
--
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
: maverick
Details:
When I open pgadmin3 and click on right pane of the interface, it will
automatically close with the following error message.
Since this is a pgAdmin bug, you might want to report it here:
http://archives.postgresql.org/pgadmin-support/
--
Robert Haas
EnterpriseDB: http
to problems of
this type. Your best bet is to probably edit the dump before
restoring 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
thinks it's connected.
You might need to adjust the TCP keepalive parameters the slave uses
to connect to the 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
against it successfully, without (hopefully) going
overboard into irrelevant details that the user doesn't need to care
about.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
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
PQgetResult() is called, we read enough data from the connection
to create and return one result object
previously issued, and
then do whatever it is you want to do next. A full connection reset
would be pretty expensive in this context and, as you might guess,
there are a lot more things that cause ERROR than there are that cause
FATAL.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
On Sat, Jan 22, 2011 at 10:44 PM, Tom Lane t...@sss.pgh.pa.us wrote:
What did you do exactly? testlibpq.c just uses PQexec(), and AFAICS the
connection status does end up BAD if the backend is terminated before a
PQexec starts.
PFA.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
that description out a bit to make it more clear that this
is really only going to tell you if TCP/IP has explicitly blown up in
your face, and not any other reason why things might not be working,
although I think there are hints of that there already.
--
Robert Haas
EnterpriseDB: http
have bad hardware.
--
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
committed the first hunk of this patch, as I think it's useful
and innocuous. The second half looks like bad grammar to 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
',
'consolidated_urls_pkey');
--
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
integers. But if it is
getting reset, it's not happening magically behind the scenes - some
human being or program is resetting it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
anyone can imagine; they mean we know that it
works this way and we haven't actually figured out a way to do any
better yet without causing other problems.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
guess the obvious question is - what happens when you try 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
getting duplicate key errors and
you drop the index, you would then get actual duplicate keys...
--
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
) returns timestamptz as $$select
to_timestamp($1,'-MM-DD HH24:MI:SS.MS')$$ set timezone = 'UTC'
language sql;
--
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
discussion seems to
be what information we pass to external auth libraries like GSSAPI or
Kerberos, given that we have host and hostaddr to choose from.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
report, although the report of *empty*
log files alongside the CSV logs seems kind of odd to me. As far as
the PGadmin questions, you probably want to try here:
http://archives.postgresql.org/pgadmin-support/
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
in heaptuple.c that can throw this error,
reproduce the problem, and then get a backtrace. But if it's
happening randomly I don't have a lot of ideas.
I do wonder if this could be related to using TIDs that don't actually
exist in the table. That might be worth some experimentation.
--
Robert
be nice to make the planner consider such plans
automatically, but that'd be tricky to make work, I think.
--
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
for the
parameter, or by changing the query to select $1::text rather than
just $1. I'm not exactly sure how to do either of those things on the
PHP side, but there's probably a way...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql
configure would emit, so I'm not totally
sure I see the point. Though on the flip side I see no real reason
NOT to add a configure check, either.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
to conclusion that can be fixed
on 8.4.4 with:
ALTER FUNCTION hstore_in(cstring) IMMUTABLE;
but is it really safe?
Or text-hstore conversion in 8.4 is really VOLATILE as labeled in
hstrore module?
I think your proposed change is safe.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
it simply silently doesn't work. Am I wrong? What happens if
you do:
SET client_encoding TO
'some_really_long_string_that_is_almost_certainly_not_a_valid_encoding';
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql
. For products closely
connected with PostgreSQL, there may be an appropriate mailing list
available.
In this particular case I think you want:
http://archives.postgresql.org/pgadmin-support/
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql
\scheduler.log
The pgAdmin folks also maintain pgAgent. You probably want to report
this bug here:
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
On Tue, Dec 21, 2010 at 11:09 PM, Tom Lane t...@sss.pgh.pa.us wrote:
So if we take the complaint seriously, we'd better patch 8.2 as well.
I'm sort of inclined to think we should take the complaint seriously.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL
unaccent() from VOLATILE to STABLE?
Sounds like it, but it doesn't sound like it will help much. :-(
--
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
?
--
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
I'm willing to put in...
Any way you can get a stack backtrace at the point the error occurs?
--
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
this is not broken for everyone, or we would have heard about
it before now.
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
My guess is that the first thing you need to do is look for a log file
that contains more specific information about the cause of the
failure.
--
Robert Haas
EnterpriseDB
explanations upthread.
--
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
Yeah, parameter substitution doesn't work in this case. You could
however build up a string with quote_identifier() and then EXECUTE the
resulting string.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
the
design should be).
--
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
module is used.
Pavel Stehule already prepared a fix (see the attachment).
I don't see a response to this email, but it looks like Tom did apply a fix.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
to start. Verify
that you have privileges to start system services. ( Retry or Cancel)
You need to contract Poker Tracker support about this. We don't have
any control over how their installer sets things up.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL
be convenient if it worked differently.
Nobody's felt the urge to do the work necessary to remove that
limitation yet, though...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
the values to be all
the same datatype.
ok, can I send a patch?
In the part of Tom's email you didn't quote, he wrote this can't
work. Did you miss that part?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql
: Unable to create view with parameter in PL/pgsql
Details:
Below is simple test case. Perhaps, I'm doing something wrong.
You can accomplish what you're trying to do using EXECUTE.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql
if we did it that way on purpose, but it seems
like testing for actual group membership would be less surprising.
--
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
DATABASE, and REINDEX DATABASE.
I'm not sure if there's some generic way we could refer to all that
rather than listing them all individually.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
On Sun, Nov 28, 2010 at 11:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Nov 23, 2010 at 10:29 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I believe the definition of in role we use here is has the privileges
of role. Since kaiting.chen is a superuser
at breakpoint. The same happens in versions 8.3.11
and 8.3.10. The last version where debugging worked was 8.3.9.
I think you may need to talk to the pgAdmin folks about this.
http://archives.postgresql.org/pgadmin-support/
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
On Thu, Nov 18, 2010 at 10:28 AM, Jon Nelson jnelson+pg...@jamponi.net wrote:
On Wed, Nov 17, 2010 at 8:57 PM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Nov 16, 2010 at 10:48 AM, Jon Nelson jnelson+pg...@jamponi.net
wrote:
I have a process which runs in parallel creating tables which
://jdbc.postgresql.org/documentation/84/callproc.html#callproc-resultset-refcursor
This seems likely to be related to the OP's problem, because his code
snippet does in fact show him calling getObject()...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
a big fat lock to prevent
such an issue.
The ALTER TABLE generates that error? Is it running concurrently with
any other DML? What version of PostgreSQL is this?
That does sound like a bug.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent
coax a stack trace out of
pg_dump?
--
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
: cannot alter column
Details:
if column is used by view or function,I will alter the column,then the
system notice:rule _RETURN on view mop3000c_view depends on column
cust_cono
It does do that, but I don't think it's a bug.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
is to make the DEF files be generated in the
builddir, to complete the intention of the latter patch.
Is anyone working on that?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
On Fri, Oct 29, 2010 at 1:56 PM, Tom Lane t...@sss.pgh.pa.us wrote:
But for user-facing parameters I agree we should do it,
and ssl_ciphers is one of those.
+1.
In any case, a doc patch would be the right thing for the back branches.
+1.
--
Robert Haas
EnterpriseDB: http
On Oct 29, 2010, at 4:21 PM, Kevin Grittner kevin.gritt...@wicourts.gov
wrote:
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Robert Haas robertmh...@gmail.com wrote:
I think if I had to pick a proposal, I'd say we should disable
#2 for the specific
On Oct 29, 2010, at 5:53 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Yeah, I think we're going to have to live with it, at least for 8.4. One
could make an argument that 9.0 is new enough we could get away with a small
behavior change to avoid a large
setting that's incompatible with the
filesystem, maybe we should add a HINT. This makes two reports today,
plus apparently at least one more on the Ubuntu sight.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list
fazer?
grato pela atencao.
paulo pillon
This looks like a request for help, not a bug. Also, this is an
English-language mailing list. You might want to try here:
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
given all of the ways people may choose to make a backup.
--
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
approximately true. I'm not sure why
Teodor implemented it like that instead of using the type's real
comparison functions, but it's pretty much useless if you want the
same sort order that the type itself defines.
Are you planning to fix this?
--
Robert Haas
EnterpriseDB: http
the makers of that software rather than us. It is their
installer that has installed PG, in all likelihood, and we don't have
any control over (or knowledge of) what it does.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list
?
I would expect that to 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 subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
: could not create
shared memory segment:
This seems like it might be a bug. Can we fix it by initializing...
something... a bit more thoroughly than we presently do?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
and resubmitted for the
then-current open CommitFest, which can always be found at:
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
of duplicated schemas, as many times as the number of the tables in the
schema.
You may want to report this problem here:
http://archives.postgresql.org/pgsql-odbc/
This list is for bugs in core PostgreSQL.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
I might be lagging behind.
I didn't get it either. The original report was posted to pgsql-bugs
on October 10.
--
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
. Also, please specify
which 8.1.x release you are running.
--
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
('gfds', null::text));
avals
---
{}
(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/pgsql-bugs
is up? Or look at pg_stat_activity? What is
it doing during all that time?
--
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
it).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres 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 Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
it
by hand without --binary-upgrade?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres 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 Mon, Sep 27, 2010 at 12:44 PM, Ashesh Vashi
ashesh.va...@enterprisedb.com wrote:
We're happy to see the problem resolved on your end. :-)--
However, it doesn't seem that we've actually done anything about the
underlying issue with pg_ctl.
--
Robert Haas
EnterpriseDB: http
://www.postgresql.org/docs/current/static/bug-reporting.html
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
chunks);
485870536 used
which is well beyond the configured memory limits (280MB shared_buffers,
temp 32MB, workmem 64MB)
Are you sure you meant to report this here? Seems likely to be a
Slony issue, although of course I'm not sure of that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
for the installers - we don't see
enough demand for it to justify the testing requirements I'm afraid.
So I think what that means for the OP is that he should install
PostgreSQL by some other method - for example, apt-get, or compiling
from source.
--
Robert Haas
EnterpriseDB: http
On Wed, Sep 22, 2010 at 9:04 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Can SHOW return a NULL value, rather than the empty string?
I think that would take some work in guc.c, and likely a redefinition
of the API for show-hook functions. I'm not excited
out of memory. :-)
What is the value of maintenance_work_mem? How large is the table?
How much memory do you have on your machine? Exactly which 8.4
release are you running?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing
SHOW return a NULL value, rather than the empty string?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
are not having this
problem, because otherwise it's pretty hard to fix.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
mentioned).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Windows troubleshooting meme... if you
reboot, does that fix it?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
, is it possible to make both cases work?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
breath.
I wonder if Merge Append could be made to help with this case.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
On Sun, Sep 12, 2010 at 12:40 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Aug 31, 2010 at 10:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
We are not going to try to enforce uniqueness. This has been debated
before, and most people like the current
question
on StackOverflow website.
http://stackoverflow.com/questions/3597000/postgresql-9-0-an-empty-row-with-
null-like-values-in-not-null-field
Can you send us the results of:
pg_dump -t st_daily2
and the results of doing this in psql:
\d st_daily2
--
Robert Haas
EnterpriseDB: http
On Sat, Feb 6, 2010 at 9:09 PM, Chris Travers ch...@metatrontech.com wrote:
On Sat, Feb 6, 2010 at 2:36 PM, Robert Haas robertmh...@gmail.com wrote:
That's really odd. Nothing pgAdmin does should be able to crash the
PostgreSQL server, I would think. Have you got any custom code loaded
the functions which fail for the automated analyze process.
Can this be a search_path problem?
Maybe you should do ALTER FUNCTION name SET search_path = 'the right
search path' and see if that helps.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via
On Wed, Aug 18, 2010 at 9:55 AM, Jens Wilke jens.wi...@affinitas.de wrote:
uuid-ossp.c:29:2: error: #error OSSP uuid.h not found
This seems like the one to look at. Perhaps you need to apt-get
install the package that contains that file.
--
Robert Haas
EnterpriseDB: http
than tables. This would be good to
fix, but probably we'd need to start by coming up with a coherent
overall plan.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
log_min_duration_statement=0 and then find 'em in the logs.
If you do this with some trivial query in the places where you have
some queries here, it doesn't crash.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
On Wed, Aug 11, 2010 at 5:12 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
In theory, the optimization Brian wants is possible here, right? I
mean, you could replace the functional call with a Param, and pull the
Param out and make it an InitPlan. Seems
On Thu, Aug 12, 2010 at 10:44 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Aug 11, 2010 at 5:12 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Yeah, possibly. It would probably be difficult for the planner to
figure out where the cutover point is to make
subexpression trees. It would be nice to
figure this out at some point in the process where we already have to
check volatility anyway.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
.
An even better idea might be to uninstall PostgreSQL using Add/Remove
Programs, or whatever uninstaller came with the installer you used.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
, top2);
alter table bottom no inherit something;
If something = top1, then bottom.a should now allow nulls, but if
something = top2, then it should still be not null. Unfortunately,
we don't do enough bookkeeping right now to distinguish those cases.
--
Robert Haas
EnterpriseDB: http
* that
the results won't change for a given set of arguments, not that it is
*required to prevent* it from being called multiple times with the
same set of arguments.
You can certainly prevent the function from being inlined, though
(perhaps, by writing it in PL/pgsql).
--
Robert Haas
EnterpriseDB: http
---
Function Scan on f (cost=0.25..12.75 rows=5 width=4) (actual
time=34.585..51.972 rows=1 loops=1)
Filter: (f = 1)
Total runtime: 63.277 ms
(3 rows)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
to the correct mailing list, which is
pgsql-performance.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
301 - 400 of 731 matches
Mail list logo
