on I even tried it is that I was testing for a
PostgreSQL bug -- but we should fail gracefully, e.g. "Use of prepared
statements with pgbench requires persistent connections. You may not
use the -C and -m prepared options together".
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.
ed in state 7: ERROR: prepared statement "P0_7" does not
exist
Client 2 aborted in state 7: ERROR: prepared statement "P0_7" does not
exist
transaction type: TPC-B (sort of)
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pg
e, the
> problem shows.
>
> I know that it's probably not a big deal for most of the people, but it
> did bite me, so I'm reporting it.
It has been a nuisance for me too. Possible patch for pg_ctl is in the next CF:
http://www.postgresql.org/message-id/cak3ujrfk8-izau1s
On Thu, May 16, 2013 at 3:33 PM, Josh Kupershmidt wrote:
> Backtrace looks like this:
My mistake -- the last backtrace was from an idle client before the
crash. Thank you andres and wulczer for the correction. Here is the
interesting one:
(gdb) bt
#0 has_unnamed_full_join_using (jtnode=0x0)
c:1244
#10 0x000100194089 in main (argc=3, argv=0x100800700) at main.c:196
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
a very simple reproduceable one so
far have met with failure. So I'm filing this bug *in case* we see other
issues with repetitive RESET ROLE calls in the future.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To
Folks,
So I'm a bit surprised that this bug report hasn't gotten a follow-up.
Does this sound like the known 9.2.2 corruption issue, or is it
potentially something else?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
Alvaro,
BTW, we haven't been able to reproduce this crash deliberately, yet.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
to include a call to setval() to set a
sane value for the sequence. For the record, reimplementing pg_dump is
usually a bad idea.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Mark,
I have PL/R and PL/v8 installed on that server (as well as a few other
extensions). However, neither of those is invoked in the procedure
which caused the crash; it's straight PL/pgSQL.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing
On 03/08/2013 07:27 PM, Alvaro Herrera wrote:
> Josh Berkus wrote:
>> Folks,
>>
>> This is one I've never seen before:
>>
>> => select generate_master_tables();
>> WARNING: AbortTransaction while in COMMIT state
>> PANIC: cannot abort transa
is not the normal failure for that.
Note that the tables were, in fact, created, and as far as I can tell
there's no corruption of the database.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to y
s to find the range type for timestamptz. Why can't it?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ar fixes. I could clean these up for you in a later version if
you'd like.
4. There seem to be spurious whitespace changes to the function
prototype and declaration for _printTocEntry.
That's all I've had time for so far...
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
dropdb and dropuser both support a similar option named --if-exists. I
suggest --if-exists instead of --conditional-drops for consistency.
I've only glanced at the patch, but if it makes no sense to use
--conditional-drops (or --if-exists, whatever it ends up being called)
without --clean, th
ation | RowShareLock| test1
relation | AccessExclusiveLock | test1
I understand why establishing an FK needs an ExclusiveLock on the
referenced table, but it doesn't need an AccessExclusiveLock. This
causes lots of deployment issues for users.
--
Josh Berkus
PostgreSQL Experts I
nt from
\d *
both in the format of the output, and that the latter displays
pg_catalog tables. At any rate, you can use:
\dtv *.*
for all tables and views in all schemas. (Unfortunately, you are then
stuck with noise from pg_catalog and information_schema.)
Josh
--
Sent via pgsql-bug
Jeff, Hackers:
Is there a strong reason why this has to error?
postgres=# select '[,]'::TSTZRANGE
postgres-# ;
tstzrange
---
(,)
(1 row)
postgres=# select '[, ]'::TSTZRANGE;
ERROR: invalid input syntax for type timestamp with time zone: " "
LINE 1: se
bugs/2011-10/msg00210.php
and at least there's a doc note now warning against using relative
paths, though it sure would be nice if we could fix this gripe.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/
ath.
> Not sure about what a useful solution would be.
I may not have time to look at this today, but I think this behavior
worked fine in the last version[1] of Gurjeet's \ir patch which I
reviewed, which had different behavior for pathname normalization than
what got committed.
Josh
mes to -100, which gets picked up here:
commonLen = Min(commonLen, SPGIST_MAX_PREFIX_LENGTH);
and ultimately palloc'ed as a size. I'm not sure what'd be the right
way to fix this after reading the comment above
SPGIST_MAX_PREFIX_LENGTH, but thought I'd share.
Josh
--
Sent
9.2beta2 server showed in his version() output. There's a reason we
print out a warning like this:
WARNING: psql version X.a, server version Y.b
Some psql features might not work.
when the major version of psql and the server it is connecting to don't match.
Josh
--
Sent vi
to submit for the open CF?
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ht bug,
though there are e.g. non-kosher uses of malloc() which could
certainly be improved.
Hrm, I wonder if proc_exit() and ExitPostmaster() could be declared
with __attribute__((noreturn)) , that seems like it would quiet a few
errors.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql
On Fri, Jun 1, 2012 at 11:38 AM, Anna Zaks wrote:
> Josh,
>
> What kid of machine are you using? Please, let me know how long it
> took after it's done (It takes about one and a half hours on mine).
It just finished, actually: took about 7 hours to run, not counting
the tim
turns false. But IMO it's worth fixing anyway,
to keep the compilers happy or in case of future code calling
buildACLCommands() or parseAclItem().
Attached is a patch to hopefully fix those two errors. I couldn't
quite verify this fixes the OP's error messages, since "checker-266"
i
.3. Have you
> perhaps changed any server settings?
I only get the error if I:
SET standard_conforming_strings TO off;
otherwise, it works fine. Perhaps it's still worth fixing though.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
tracker to put it in so the next time someone is working on the log
collector for other reasons they can tweak this too, or when some new
hacker wants an easy first patch.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@po
16:38:21 PDT [10181]: [1-1] user=,db= LOG: could not open
log file "/pglogs/check/logs/datacollection-2012-04-26-16-38": No such
file or directory
2012-04-26 16:38:21 PDT [10181]: [2-1] user=,db= LOG: disabling
automatic rotation (use SIGHUP to re-enable)
So, yes, exactly.
--
Josh Be
t a bogus new value of
> log_directory, eg not there or not writable by postgres. In any case,
> if this is the locus of the problem, there ought to be instances of that
> log message in the active log file. (Josh?)
Aha.
Yeah, the problem is, directory permissions to the contrary, somethin
> Do you want to try attaching to the collector with a debugger and seeing
> if it ever gets into the "if (got_SIGHUP)" block in SysLoggerMain?
Hmmm. No debugger on this system, not unexpectedly. I'll see if I can
get authorization to add one.
--
Josh Berkus
Postgre
On 4/26/12 5:50 PM, Tom Lane wrote:
> Josh Berkus writes:
>> Summary: despite pg_reload(), log directory, filename and destination
>> don't change
>
> Looking at the code, it's really hard to see how this could possibly
> happen, unless maybe the process is
to get to the bottom of it.
I also tried a sighup to the logger process, with no effect.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 4/26/12 3:48 PM, Tom Lane wrote:
> Josh Berkus writes:
>> Also, have we discussed maybe hiding these schemas from \dn?
>
> We've done more than discuss it:
> http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=e43fb604d6db229d70d3101aa53348cc16a54
On 4/26/12 11:22 AM, Tom Lane wrote:
> Josh Berkus writes:
>> summary: database has 291 empty pg_toast_temp schemas.
>
> If your max_connections is 300 or more, this isn't surprising in the
> least.
Yes, they are.
>> ... so, apparently we still have an issue w
temp_%';
schemaname | relname
+-
... so, apparently we still have an issue with cleaning up pg_toast_temp
schema?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscrip
e.g.
SELECT
(CASE WHEN substr(my_column, 1, 2) ~ '[0-9][0-9]'
THEN substr(my_column, 1, 2)::int
ELSE 99
END)::int
FROM my_table;
By the way, LIKE in your example was incorrect: I think you wanted
either 'SIMILAR TO' or the '~' operator depend
chd.conf,
/etc/profile, /etc/bashrc, ~/.bashrc, ~/.bash_profile,
~/.MacOSX/environment.plist, and so on.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
es in fact mention that contrib
modules will need to be installed by a superuser, so this restriction
is not entirely undocumented.
Josh
[1] http://www.postgresql.org/docs/devel/static/contrib.html
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscrip
t an error. But if no
>>> input, however misguided, should ever cause that symptom, then it's, I
>>> don't know what the terminology should be, say, a "severe error".
>>
>> +1
>
> I'm strongly in favour of this.
This is *so* not
of thing.
Huh? I don't follow you at all Peter.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 1/28/12 5:27 PM, Tom Lane wrote:
> Josh Berkus writes:
>> SUMMARY: if you attempt to UPDATE or DELETE FROM a parent table in an
>> inheritance relationship using a wCTE, you get the following error message:
>> ERROR: could not find plan for CTE
>
> Fixed, tha
arent using wcte where val = whichtab;
ERROR: could not find plan for CTE "wcte"
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
inked to that
emphasizing this would be a good idea. Did you have a specific spot in
the manual in mind for such a note, or a preferred wording?
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
hared_buffers by a quarter or so ought
> to do as a workaround, till you figure out what's going on.
>
> regards, tom lane
>
Wow, that's interesting, though I can't say I'm completely surprised.
You were spot on about turning down shared_buffers - I'm trying it at
96MB, down from 128MB, and the recovery process is chugging along.
I'll probably just ditch this VM and hosting provider (chvps aka
privatelayer, in case anyone wants to stay away).
Thanks for the investigation!
Josh
--
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, Nov 30, 2011 at 10:50 PM, Tom Lane wrote:
> Josh Kupershmidt writes:
>> On Wed, Nov 30, 2011 at 9:17 PM, Tom Lane wrote:
> It might be worth recompiling at -O0, first to see if that changes the
> behavior and second to see if it changes the reported stack trace.
Her
On Wed, Nov 30, 2011 at 9:17 PM, Tom Lane wrote:
> Can you try that on 9.1 branch tip to see if it's already fixed?
Hrm, don't think that helped - I get the same error in the logs using
a checkout of branch REL9_1_STABLE.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postg
artitioned table.
Since the standby VM is new (I've used the same hosting provider
before, but this is the first time I tried an Ubuntu VM), it's
entirely possible I messed something up in the set-up. Or it could be
some flakiness with the VM itself.
But before I start blowing things away
en't verified this (the way to check would be to do
a git checkout of the 9_1_STABLE branch from git, and see if the fix
is present there).
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
cript.sql
>
> I expect the parser to load and execute my-script.sql located within
> /some/path/to/sql/script/dir
Yup, that works on a 9.2dev client:
test=# \set my_dir /tmp/foo/bar/baz
test=# \i :my_dir/test.sql
?column?
--
1
(1 row)
with test.sql containing the single l
ntly, such as
928311a463d480ca566e2905a369ac6aa0c3e210, so maybe this case got fixed
as a nice side-effect.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
> The least painful solution might be to always quote *every* identifier
> in commands sent to the source server, since we don't especially care
> how nice-looking those are.
I've never been clear on why we don't do that in the first place.
--
Josh Berkus
Post
reserved word and quote it before dumping. 9.0 and
later pg_dump does not. Any ideas?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
> Seems you have a sequence called "new"; seems we don't handle that
> well.
Hmmm ... yes, you're correct. Idiot users.
Interestingly, the sequence is no problem until 9.0. 8.4 handled it
fine. I'd guess this is another example of where merging in plpgsql
br
he sequences is getting mangled. Any
clue how?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ects win1252.
I think it's quite possible that this is something broken in the win1252
encoding itself. I've seen a lot of reports online for errors from
other software. However, we need to at least find a workaround for
users if we can't fix it ...
--
Josh Berkus
PostgreSQL Exper
pg_ctl -D /tmp/foo/bar/baz/ start
and I was under the impression (supported by the pg_ctl doc page,
which claims "restart mode effectively executes a stop followed by a
start") that these sequences should be equivalent.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
"pg_ctl -D $DATADIR start" should work at this point, though. This
seems like some bug in normalizing the absolute path to
postgresql.conf.
Josh
pg_ctl_weirdness.sh
Description: Bourne shell script
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
> \copy is different because it uses OT_WHOLE_LINE mode to read the
> argument, and that doesn't expand :variable references. I'd be a bit
> leery of changing that.
So, doc warning then?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs
enum values.
Not exactly; that code is rife with race conditions. For instance, how
does the "Check data references" loop ensure that previously-checked
tables don't get a new row containing the forbidden enum_elem before
the function is finished?
Josh
--
Sent via pgsql-bugs mailing
> It's possible that we could build simple estimators for these operators
> that just turn the problem into a range estimation and then pass it off
> to somewhere else, but nobody has tried.
Right, that's why I'm asking. I'd like to reuse code ...
--
Josh Berkus
estimate the cost of the indexscan, why can't we estimate the
rowcount? Sorry if I'm being dense here, but I really don't understand
how the special operator code works at all.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@
On 9/21/11 1:56 PM, Tom Lane wrote:
> Josh Berkus writes:
>> Summary: special inet operators ( << >> <<= =>> ) are
>> up to 100X off in estimating rowcounts
>
> A look in pg_operator will show you that these operators have no
> associated
'87.178.193.255'::inet))
Total runtime: 0.097 ms
Note that the mis-estimate of rows returned in each case is almost
exactly 50% of the total rows in the table. That would suggest that
match_special_index_operator is failing, and not recognizing the <<=
operator for est
-resources.html
See the "MacOS X" section on that page for OS X specific instructions.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
variables work perfectly fine with COPY. It's just \copy
which seems to be misbehaving.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
fact they
are undefined. For example, if you try to use variable NEW in a delete
trigger, you'll get an error message like:
| ERROR: record "new" is not assigned yet
| DETAIL: The tuple structure of a not-yet-assigned record is indeterminate.
How about a doc tweak like the atta
oks like we're not successfully escaping characters on WIN1252.
The characters in question are also latin characters.
We've reproduced this on a clean install.
--
-- Josh Berkus
PostgreSQL Experts Inc.
n into it somewhere I can do a stack trace ...
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chan
::1/128 trust
If you're still having trouble, post the uncommented lines from your
pg_hba.conf file, and also post lines about connection attempts from
your PostgreSQL server log file after you've turned on
log_connections.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
result in
unsurprising values of Show TimeZone.
(This issue was reported by a customer as a bug to us)
I'll give some thought as to how we could do so, and maybe add it to the
TODO list.
--
-- Josh Berkus
PostgreSQL Expe
On 3/3/11 2:31 PM, Josh Berkus wrote:
> uname -a
> Linux hemingway 2.6.32-25-server #44-Ubuntu SMP Fri Sep 17 21:13:39 UTC
> 2010 x86_64 GNU/Linux
>
> date
> Thu Mar 3 15:30:17 MST 2011
Also:
echo $TZ returns nothing. We've checked several Ubuntu systems, and it
seems t
as on how this happened?
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to
Thank you both for clearing that up (and doing so quite quickly!).
The behavior makes complete sense now that I understand what is
happening here behind the scenes.
Regards,
Josh
On 3/3/2011 11:24 AM, Tom Lane wrote:
"Joshua McDougall" writes:
When using the pg_notify(text,text
On 1/26/11 12:13 PM, Tom Lane wrote:
> Josh Berkus writes:
>> Oh! Actually, it only *did* 27 runs. So it actually completed building
>> the index. I'd expected trace_sort to give me some kind of completion
>> message; apologies for not checking all screen windows.
&g
as usual, I've completely mislocated the bug. I'll need to rerun
the pg_restore and actually diagnose *that*.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent
this index run at 7pm PST
yesterday and it's been 15 hours, not 2 as the elapsed time would suggest.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent vi
e index, rows would be more randomly distributed.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscr
On 1/25/11 1:21 PM, Tom Lane wrote:
> Josh Berkus writes:
>> Note: I have this running now on a test box. If someone responds in the
>> next couple hours, I can run whatever diagnostics you want on it.
>> Otherwise I'll kill it off and start over with debug logging
x27;ll try to run a sort_trace on an 8.4.4 copy of the database.
Oh, FWIW, the rough number of rows in the table:
1 486 530 000
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.
On 1/25/11 1:21 PM, Tom Lane wrote:
> Josh Berkus writes:
>> Note: I have this running now on a test box. If someone responds in the
>> next couple hours, I can run whatever diagnostics you want on it.
>> Otherwise I'll kill it off and start over with debug logging
The current index build run has been going
for almost 100 hours.
More detail:
mainentance_work_mem = 1GB (out of 32GB RAM available)
9.0.1 was built from source, using Sun CC
for the current test, I'm running with fsync off
(but I've had the same issue with fsync on)
Ideas?
(* object names have been changed to preserve confidentiality)
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
you didn't specify on the command line.
Simple doc patch attached. I think the "Examples" section demonstrates
that createuser will prompt for this information without having to
belabor this point in the doc.
Josh
diff --git a/doc/src/sgml/ref/createuser.sgml b/doc/src/sgml/ref/creat
t; is unavailable if the server was not compiled with support for SSL"?
Exactly. If you don't get around to it, bug me in January.
--
-- Josh Berkus
PostgreSQL Experts Inc.
htt
s only available
if PostgreSQL was built with SSL support").
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresq
: unrecognized configuration parameter "ssl_ciphers"
So, did ssl_ciphers go away on purpose? If so, why? If not, why isn't
it accessible?
--
-- Josh Berkus
PostgreSQL Experts Inc.
st surprised Postgres didn't throw an error.
The only mild concern I have is if this could possibly lead to
ambiguous parsing in some situations, though I've played with some
examples and I haven't seen any yet. It would be nice to have this
behavior documented somewhere though.
Josh
On Thu, Oct 28, 2010 at 8:01 PM, Tom Lane wrote:
> "Josh Kupershmidt" writes:
>> I noticed that Postgres in many cases will happily tokenize WHERE clauses
>> having no space between a condition and "AND" or "OR".
>
> This has nothing to do w
The following bug has been logged online:
Bug reference: 5732
Logged by: Josh Kupershmidt
Email address: schmi...@gmail.com
PostgreSQL version: 8.3 and HEAD
Operating system: Linux and OS X
Description:parsing of: "WHERE mycol=123AND ..."
Details:
I no
I discussed this report with James Pye already, and he beleives it's a
configure script bug which should be fixed before release. Anyone
capable of taking it on?
Original Message
Subject:[TESTERS] Configure/Build 9.0 rc1 - cannot build against
python3.1, with two vers
be worth asking a few interface developers what this will break.
However, given that the issue has existed for a year or more and I'm the
first one to report it formally, it clearly isn't that huge of an issue.
Any idea what version this got broken in?
--
the table owner can create
a serial column" ).
--
-- Josh Berkus
-----
Josh Berkus PostgreSQL Experts Inc.
CEO database professionals
josh.ber...@pgexperts.com www.pgexperts.com
1-888-7
he user passed an ORDER BY or not.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to you
to have a pretty darned
solid pg_upgrade because of it.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To mak
ment.
If it's causing bugs, drop it now. If we include it in 9.0, we're stuck
with it for years.
I'm OK with forcing an initDB for RC1.
--
-- Josh Berkus
PostgreSQL Experts Inc.
this, I get the following warning at
PostgreSQL startup time:
Loaded module "auto_explain"
Not safe to send CSV data
And on checking, auto-explain is indeed NOT sending anything to the
csvlog. It's not sending anything to the regular log, either.
--
On 7/7/10 1:50 AM, Magnus Hagander wrote:
> BTW, if you post bug reports to -bugs, it'll make a lot more people see them.
Sure, we just want to verify that it *is* a possible bug (and not pilot
error) first.
--
-- Jos
iciency.
Yes, I'd say that documentation is the answer, given. Hmmm are
double-quotes respected in postgresql.conf, though? Need testing.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http:/
Severity: minor
Tested On: 9.0b2, 8.4.4
Platform: SUN SPARC 4u Enterprise 450 Quad, presumably Solaris 10
Repeatable? Yes
Description:
See thread:
http://archives.postgresql.org/pgsql-testers/2010-06/msg00020.php
--
-- Josh Berkus
that easy here
without adding undue complexity. So considering no one else has
reported it at least than I've been able to find, +1 for leaving it as
is. Just thought I'd post it in case anyone has any better ideas for
tackling it.
- Josh
--
Sent via pgsql-bugs mailing list (pgsql
1 - 100 of 253 matches
Mail list logo
