be able to find all the calls to ExecutorStart() by
using grep. But it sounds like you might be better off implementing
this as an executor hook. Or perhaps one of the existing ones
(auto_explain or pg_stat_statements) would give you what you need.
--
Robert Haas
EnterpriseDB: http
should be included in the
parameter passed to the .Run function.
Is this the EDB one-click installer you're using, or something else?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
pretty sure that we don't have a directory called
pg_twoface, though it would pretty funny if we did. It's fairly
obvious what this is meant to say, but it doesn't.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql
; it looks more like your installer isn't
configuring it properly.
--
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
, but I remember this was discussed before. Perhaps we need a
note somewhere about multi-argument aggregates.
--
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
On Wed, Aug 4, 2010 at 11:29 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Oh, yeah. I guess you need this:
select thing, string_agg(stuff, ',' order by stuff) from agg_test
group by thing;
Rather than this:
select thing, string_agg(stuff order by stuff
, there is no such mode...
--
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 Wed, Aug 4, 2010 at 12:44 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I suppose this confusion is only possible because string_agg has both
a one-argument and a two-argument form.
Right, or at least that's what allows the mistake to go through without
On Wed, Aug 4, 2010 at 1:04 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Aug 4, 2010 at 12:44 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I suppose this confusion is only possible because string_agg has both
will be rc1.
--
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
important argument first, and no one would see the delimiter
as the most important one.
Well, it would match the syntax of things like perl's join(). But I
think that's probably not enough reason to go fiddling with it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres
On Wed, Aug 4, 2010 at 6:19 PM, Tom Lane t...@sss.pgh.pa.us wrote:
for: tgl, josh, badalex, mmoncure
against: rhaas, thom
Anybody else want to vote, or change their vote after seeing the patch?
If we're not regarding this as beta-forcing, I abstain.
--
Robert Haas
EnterpriseDB
rows)
Does it help if you put a CHECK (false) constraint on the parent table?
--
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
On Tue, Jul 27, 2010 at 7:27 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Does it help if you put a CHECK (false) constraint on the parent table?
It won't --- it'll still result in an append plan even if there's only
one surviving child.
This is one
? Then it
would be hard to tell whether migration was safe or not. Perhaps the
right long-term solution is to try harder to preserve OIDs in more
cases.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
as far back as 8.3, due to the
lazy XID assignment changes in that version, but it looks like the bug
exists all the way back to 8.0. It looks like only minor adjustments
are required for the older branches, though. 7.4 is not affected, as
it does not have subtransactions.
--
Robert Haas
On Thu, Jul 22, 2010 at 5:01 PM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Jul 19, 2010 at 4:35 PM, Andres Freund and...@anarazel.de wrote:
Well. I got that far. But why is that something worthy of support?
For one I have a hard time imaging a sensible use case, for another doing
calculated
(heap_(insert|update|delete) basically) after youre deeply stacked.
Thanks, perfect. Committed and back-patched to 8.0.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
, it looks like some kind of
installer...
The installer apparently isn't too smart, either, because the
second-to-last name of our product is the 17th letter of the alphabet,
not the 15th.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql
, so you should probably choose a
more appropriate mailing list on which to ask this question. You'll
probably have better luck if you provide a few more details about what
your setup is and what you're trying to do with it.
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
--
Robert
this subject on this place, because it is an overall
problem with the installation of postgresql with all the modules using this
type of icon.
Thank you
regards
*** heinz ***
PostgreSQL itself doesn't have icons. Perhaps this is a pgadmin issue?
http://www.pgadmin.org/support/list.php
--
Robert
- it could be less.
But I agree with you that the estimate of 1000 doesn't seem to make
much sense. I'm not sure where that's coming from.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
why
is permission denied ?
the set role is in a security invoker function before the delete statement.
Could this be related in anyway ?
I tried it here and it worked for me. Can you provide a
self-contained test case?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
records works 7 sec)
SELECT d1.ID, d2.ID
FROM DocPrimary d1
JOIN DocPrimary d2 ON d2.BasedOn=d1.ID
WHERE (d2.BasedOn=234409763) or (d2.ID=234409763)
EXPLAIN ANALYZE output for both queries, please?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent
10.6.4)
Description: Makefile.darwin broken
Details:
Makefile.darwin references src/backend/postgres, which doesn't exist.
So what, specifically, is not working for you? I'm using MacOS X
10.6.4 x86_64 also, and I can build Postgres without a problem.
--
Robert Haas
EnterpriseDB: http
/Guide_to_reporting_problems
--
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 Thu, Jun 24, 2010 at 11:02 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Jun 24, 2010 at 4:50 PM, Chris Browne cbbro...@acm.org wrote:
alvhe...@commandprompt.com (Alvaro Herrera) writes:
Excerpts from Chris Browne's message of jue jun 24 14:40:30 -0400 2010:
robertmh...@gmail.com
problem
has been fixed in AIX 6.1. It would be good to understand that.
--
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
On Thu, Jun 24, 2010 at 4:50 PM, Chris Browne cbbro...@acm.org wrote:
alvhe...@commandprompt.com (Alvaro Herrera) writes:
Excerpts from Chris Browne's message of jue jun 24 14:40:30 -0400 2010:
robertmh...@gmail.com (Robert Haas) writes:
This patch makes it clear that the workaround
have tried disabling the firewall etc.
I suspect ODBC is not compatible with windows 7.
I have been able to set it up and got it working
on Vista, XP for
serveral years.
You may want to try this question on the pgsql-odbc mailing list.
http://archives.postgresql.org/pgsql-odbc/
--
Robert
://archives.postgresql.org/pgsql-odbc/
--
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
do you think that? I tried both the example you gave here and the
example from your followup email on the 15th in 9.0beta, and the
behavior seems correct there.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql
think this might be their
mailing list though - maybe you want to try there?
http://pgfoundry.org/mailman/listinfo/npgsql-devel
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
, and there are plenty of people on this thread
saying either (1) they don't want to do what you're proposing or (2)
their application doesn't need fixing because it already quotes
everything.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via 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
Was this discussed change made? Was it backported, or only applied to head?
I believe this is the commit:
http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=3a524653d18f29676b91f740634a673b72beb6b5
It looks like the code was changed, but I don't see any doc updates.
--
Robert Haas
On Thu, Jun 10, 2010 at 9:39 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I believe this is the commit:
http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=3a524653d18f29676b91f740634a673b72beb6b5
It looks like the code was changed, but I don't
to separate schema and data dumps without tanking performance is a
good one, too, but I still think this has merit even if we do that.
Just because we make it easier to manually edit dump files is not a
reason not to create options that render it unnecessary in the first
place.
--
Robert Haas
On Wed, Jun 9, 2010 at 2:58 AM, Dean Rasheed dean.a.rash...@gmail.com wrote:
On 9 June 2010 03:48, Robert Haas robertmh...@gmail.com wrote:
Er, I should also say, thanks for the report, and please test. I am
definitely not an expert on YAML.
I'm not an expert on YAML either, but I don't
On Wed, Jun 9, 2010 at 7:23 AM, Dean Rasheed dean.a.rash...@gmail.com wrote:
On 9 June 2010 12:07, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 2:58 AM, Dean Rasheed dean.a.rash...@gmail.com
wrote:
On 9 June 2010 03:48, Robert Haas robertmh...@gmail.com wrote:
Er, I should
On Wed, Jun 9, 2010 at 8:46 AM, Dean Rasheed dean.a.rash...@gmail.com wrote:
On 9 June 2010 03:48, Robert Haas robertmh...@gmail.com wrote:
please test.
Well your patch definitely fixes my original bug, and AFAICT always
produces valid YAML output now. I've only found one case where
testing, working through the list of
cool new features.
Quick, somebody give this man a cigar!
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
yet_another_yaml_fix.patch
Description: Binary data
--
Sent via pgsql-bugs mailing list (pgsql-bugs
. And we get questions about it here
regularly. Why not:
If (account exists)
prompt user to log into account
else
tell user account will be created, ask for account pw
prompt user for db superuser pw
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
On Wed, Jun 9, 2010 at 1:14 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
It's possible. I don't really see a reason not to add an = operator
for XML - does anyone else?
Yes, that was considered and rejected, IIRC. What is your definition
of equality
On Wed, Jun 9, 2010 at 10:52 AM, Dave Page dp...@pgadmin.org wrote:
On Wed, Jun 9, 2010 at 3:50 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 6:09 AM, Dave Page dp...@pgadmin.org wrote:
Please provide a password for the database superuser (${superaccount})
and service
On Wed, Jun 9, 2010 at 11:03 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Jun 9, 2010 at 9:35 AM, Dean Rasheed dean.a.rash...@gmail.com
wrote:
Does anyone care that Alias will sometimes be a string, and sometimes a
number?
After further review
On Wed, Jun 9, 2010 at 11:14 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Jun 9, 2010 at 11:03 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I still agree with Dean's original proposal: always quote the values of
strings.
I'd still rather rip the format
On Wed, Jun 9, 2010 at 12:25 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Jun 9, 2010 at 11:14 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Why not? Surely we can restrict EXPLAIN's set of key names to be safe.
It seems to me that it would be easy
On Wed, Jun 9, 2010 at 12:57 PM, Dean Rasheed dean.a.rash...@gmail.com wrote:
On 9 June 2010 17:52, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 12:25 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Jun 9, 2010 at 11:14 AM, Tom Lane t
On Wed, Jun 9, 2010 at 12:58 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 12:57 PM, Dean Rasheed dean.a.rash...@gmail.com
wrote:
On 9 June 2010 17:52, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 12:25 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert
On Wed, Jun 9, 2010 at 12:58 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 12:57 PM, Dean Rasheed dean.a.rash...@gmail.com
wrote:
On 9 June 2010 17:52, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 12:25 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert
.
--
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 Wed, Jun 9, 2010 at 9:10 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Sun, Jun 6, 2010 at 2:53 PM, Dimitri Fontaine dfonta...@hi-media.com
wrote:
Robert Haas robertmh...@gmail.com writes:
Well as Bruce said this option won't solve the OP's problem, unless
On Wed, Jun 9, 2010 at 9:35 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
I think users would rather have the restore fail, and know right away
they have an issue, than to do the upgrade, and find out later that some
of their application queries fail and they need to run
On Wed, Jun 9, 2010 at 4:47 PM, Dean Rasheed dean.a.rash...@gmail.com wrote:
On 9 June 2010 20:56, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 3:50 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Dean Rasheed dean.a.rash...@gmail.com writes:
Hmm. Well it's quite subjective, but IMO
On Wed, Jun 9, 2010 at 4:48 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 4:47 PM, Dean Rasheed dean.a.rash...@gmail.com wrote:
On 9 June 2010 20:56, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 3:50 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Dean Rasheed
that requires escaping. With this
approach, that change isn't needed.
--
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
On Tue, Jun 8, 2010 at 10:47 PM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Jun 7, 2010 at 4:14 AM, Dean Rasheed dean.a.rash...@gmail.com wrote:
Testing 9.0 beta, I found that EXPLAINing certain queries in YAML
format will produce invalid YAML, for example:
explain (format yaml) select
on the table might be enough to fix
the problem.
--
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
is that? I can't
install postgres here.
I feel like we've had this question a few times before, and answered
it, but I'm not a Windows guy and can't remember the answer. Can we
add an FAQ entry for this, or something?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
.
Tambien entre por modo a prueba de fallos y busque todo lo que tuviera
nombre postgres y lo elimine y volvi a instalar pero nada me funciona..que
puedo hacer??
Por favor pregunta aqui: http://archives.postgresql.org/pgsql-es-ayuda/
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
.
This is an English-language mailing list, but you could try here:
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
in subqueries etc).
It's possible. I don't really see a reason not to add an = operator
for XML - does anyone else?
It would need to be done by updating src/include/catalog/pg_*.h,
rather than via SQL, of course.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
like the JSON format, the less water that argument holds.
--
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
they are, and everyone else (whether they agree
with the behavior or not) is trying to explain the reasons why we
don't have them.
--
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
On Jun 5, 2010, at 4:02 PM, Dimitri Fontaine dfonta...@hi-media.com
wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
I don't think dumps must be human-readable is an argument to reject
such a switch, as long as it's off by default. And I haven't seen
any
other valid argument
On Sun, Jun 6, 2010 at 2:53 PM, Dimitri Fontaine dfonta...@hi-media.com wrote:
Robert Haas robertmh...@gmail.com writes:
Well as Bruce said this option won't solve the OP's problem, unless the
application he's using for managing the backups do use the option.
Well, that's a pretty trivial
that are totally nuts (like DELETE FROM pg_class, which causes
every subsequent connection attempt for that database to panic).
Perfection may be too much to ask for but I'd take modest
improvement...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql
On Fri, Jun 4, 2010 at 4:53 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Personally, I think it would be better to put some work into making
allow_system_table_mods a little less simple-minded. Right now,
!allow_system_table_mods prohibits you from doing
On Fri, Jun 4, 2010 at 5:13 PM, Tom Lane t...@sss.pgh.pa.us 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 are presumed
On Wed, Jun 2, 2010 at 9:38 AM, botak bota...@gmail.com wrote:
Dear sirs,
Referring to the matter above.
For your information, we are a government agency and been hosting a
management system since 2006. The system was developed with Postgres Sql and
PHP in Centos Platform. Recently, after a
to 10 and accuracy
of 2 fractional signs.
numeric is a good choice to avoid loss of precision, but can be a bit slower.
You could also try float8.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs
On Mon, May 31, 2010 at 10:11 AM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Sat, May 29, 2010 at 5:00 PM, Bruce Momjian br...@momjian.us wrote:
I have updated the patch, attached, to clarify that this returns text
arrays, and that you can force it to always return one row
this part to be something we should include in the
documentation. If we want to include a workaround, how about defining
a non-SRF that just calls the SRF and returns the first row?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-bugs
into larger transactions - the
case where the pending trigger queue exhausts system memory is an
unfortunate exception. You might want to think about, say, a thousand
transactions of a thousand records, instead of a million transactions
with one record each.
--
Robert Haas
EnterpriseDB: http
in other languages - see the following URL, under regional
lists.
http://www.postgresql.org/community/lists/
Also, you probably need to provide a bit more detail for anyone to help you.
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
--
Robert Haas
EnterpriseDB: http
for someone to help
you, like what you were doing when you got the error.
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
You might also want to try the pgsql-odbc mailing list, rather than here.
http://archives.postgresql.org/pgsql-odbc/
--
Robert Haas
EnterpriseDB: http
that we have any ability to so cope.
--
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 Tue, May 11, 2010 at 3:47 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alex Hunsaker bada...@gmail.com writes:
On Tue, May 11, 2010 at 12:42, Robert Haas robertmh...@gmail.com wrote:
I guess the question that comes to mind for me is how many other
things fall into this category. We define a lot
://en.wikipedia.org/wiki/Frog_boiling
--
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 Fri, Apr 30, 2010 at 4:37 AM, Chaminda Jayawardana
wpgchami...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5444
Logged by: Chaminda Jayawardana
Email address: wpgchami...@gmail.com
PostgreSQL version: 8.3
Operating system: Windows Server
On Fri, Apr 30, 2010 at 9:14 AM, Peter Eisentraut pete...@gmx.net wrote:
On fre, 2010-04-30 at 14:43 +0200, Andres Freund wrote:
On Friday 30 April 2010 13:56:11 Peter Eisentraut wrote:
You probably mean alpha5, unless you come from the future. ;-) That was
actually a mistake in the
On Wed, Apr 28, 2010 at 4:09 PM, Dimitri Fontaine
dfonta...@hi-media.com wrote:
Stefan Kaltenbrunner ste...@kaltenbrunner.cc writes:
As in have a (hyptothetical) tracker being subscribed to -bugs (and maybe
the other lists in the future as well) so the workflow would look like
this:
Well
On Thu, Apr 22, 2010 at 4:45 AM, Oleg sacramento_...@mail.ru wrote:
The following bug has been logged online:
Bug reference: 5434
Logged by: Oleg
Email address: sacramento_...@mail.ru
PostgreSQL version: 8.4.3
Operating system: KUbuntu
Description: select from
On Mon, Apr 19, 2010 at 5:02 AM, Peter Eisentraut pete...@gmx.net wrote:
On mån, 2010-04-19 at 09:59 +0200, Stefan Kaltenbrunner wrote:
I think we would not even need to expose the webinterface to the wider
community, what we probably want is something that let's us keep the
current workflow
On Sun, Apr 11, 2010 at 7:14 AM, Stefan Kaltenbrunner
ste...@kaltenbrunner.cc wrote:
Jasen Betts wrote:
On 2010-04-10, Stefan Kaltenbrunner ste...@kaltenbrunner.cc wrote:
Craig Ringer wrote:
Dave Page wrote:
This basically indicates that we need an issue tracker. There, look -
now see
On Sun, Apr 18, 2010 at 5:29 PM, Magnus Hagander mag...@hagander.net wrote:
On Sun, Apr 18, 2010 at 23:14, Tom Lane t...@sss.pgh.pa.us wrote:
Jaime Casanova jcasa...@systemguards.com.ec writes:
On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas robertmh...@gmail.com wrote:
On Sun, Apr 18, 2010 at 3
On Fri, Apr 9, 2010 at 4:43 AM, Dave Page dp...@pgadmin.org wrote:
On Thu, Apr 8, 2010 at 10:23 PM, Robert Haas robertmh...@gmail.com wrote:
BUG #5287: ispell dict erroneously returns lexeme on all prefix+suffix
cross products
BUG #5300: Bug on Mac OS X 10.6 and Postgres 8.4
BUG #5316
On Thu, Apr 8, 2010 at 11:13 AM, omar omarar...@hotmail.com wrote:
The following bug has been logged online:
Bug reference: 5408
Logged by: omar
Email address: omarar...@hotmail.com
PostgreSQL version: 8.0.0
Operating system: XP Professional SV2
Description:
On Fri, Mar 26, 2010 at 6:16 PM, Joshua Tolley eggyk...@gmail.com wrote:
I accidentally rejected this message while moderating -bugs, so I'm forwarding
it to the list to atone for myself. Apologies to all involved...
From: Rens Admiraal r...@rensnel.nl
Date: Fri, 26 Mar 2010 20:00:27 GMT
To:
2010/3/19 Roberto Rivera Mardones rorive...@gmail.com:
The following bug has been logged online:
Bug reference: 5383
Logged by: Roberto Rivera Mardones
Email address: rorive...@gmail.com
PostgreSQL version: 8.4.2
Operating system: Debian 5
Description:
On Thu, Apr 8, 2010 at 4:58 PM, Dave Page dp...@pgadmin.org wrote:
I can't help thinking that as a community we don't do ourselves any
favours at all by being so damn pedantic about where bugs should be
reported. What must new users think when they get chastised for
reporting a *PostgreSQL*
On Thu, Apr 8, 2010 at 5:19 PM, Robert Haas robertmh...@gmail.com wrote:
It would certainly be nice if we could just have all bugs reported
here and sort it out ourselves, but in practice that doesn't seem to
work. When installer or pgadmin bugs are reported here, they
typically don't get
On Wed, Apr 7, 2010 at 8:49 AM, Gaetan beaulieu b...@sogi.com wrote:
Hi!
I found a little problem with the CTRL-Z in the SQL command editor.
I have two files, each containing several SQL queries. sql_01.sql and
sql_02.sql.
I get the first file sql_01.sql from the menu, I run and everything
On Wed, Apr 7, 2010 at 4:09 AM, Roee s_r...@yahoo.com wrote:
The following bug has been logged online:
Bug reference: 5404
Logged by: Roee
Email address: s_r...@yahoo.com
PostgreSQL version: 8.3/8.4
Operating system: Windows XP
Description: Mirrored pgadmin GUI
On Thu, Mar 25, 2010 at 4:54 PM, Victor Vargas kamu...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5391
Logged by: Victor Vargas
Email address: kamu...@gmail.com
PostgreSQL version: 8.4
Operating system: Ubuntu Lucid
Description:
On Tue, Apr 6, 2010 at 1:06 AM, Josh Berkus j...@postgresql.org wrote:
On 4/5/10 9:16 PM, Josh Berkus wrote:
I can't see how this is anything but a bug; as far as I know, nothing in
the target list is allowed to restrict the number of rows which are
returned by the query. We should get 7
On Mon, Apr 5, 2010 at 4:37 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
John R Pierce pie...@hogranch.com wrote:
Chris Travers wrote:
Hmm... Back to the drawing board on that helper module :-).
like I said, its a big tarpit.
If you start up on this again, you might want to start a
On Thu, Mar 25, 2010 at 11:13 AM, bortdagos bortda...@ucla.edu wrote:
The following bug has been logged online:
Bug reference: 5388
Logged by: bortdagos
Email address: bortda...@ucla.edu
PostgreSQL version: bortdagos
Operating system: bortdagos
Description:
On Sat, Mar 27, 2010 at 6:06 AM, to...@tuxteam.de wrote:
I am facing problem in optimizing my this query. can u please let me know
how can i optimize this query.
this is most probably not a PostgreSQL bug. You are more likely to get
help from pgsql-nov...@postgresql.org. But to help others
401 - 500 of 731 matches
Mail list logo
