Re: [BUGS] pgBench cannot use prepared statements and reconnections

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.com -- Sent via pgsql-bugs mailing list (pgsql-bugs

[BUGS] pgBench cannot use prepared statements and reconnections

: 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 (pgsql-bugs@postgresql.org) To make changes to your

[BUGS] easy crash on HEAD

, argv=0x100800700) at postmaster.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

Re: [BUGS] pg_ctl -D /absolute/path -m fast restart - doesn't work in some cases

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-izau1smpnzr5muc+6crwbk0_7byjnwuoapj3e...@mail.gmail.com Josh -- Sent via pgsql-bugs mailing

[BUGS] RESET ROLE issue (Unreproduceable (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 make changes to your subscription: http

[BUGS] Re: BUG #7969: Postgres Recovery Fatal With: incorrect local pin count:2

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@postgresql.org

Re: [BUGS] New kind of crash?

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

Re: [BUGS] BUG #7940: Auto increment issue

. 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

Re: [BUGS] New kind of crash?

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 transaction 9387287, it was already committed Anything that causes

Re: [BUGS] New kind of crash?

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 list

[BUGS] Issue with range types and casts?

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

[BUGS] New kind of crash?

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 your subscription

Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist

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

Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist

so should raise an error. Josh -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] Why does FK creation still take an access exclusive lock on the referenced table?

| 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 Inc. http://pgexperts.com -- Sent via pgsql-bugs mailing list

Re: [BUGS] psql \d command hides objects from lower schemas

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-bugs mailing list (pgsql-bugs

[BUGS] Arbitrary whitespace restrictions on range types

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: select '[, ]'::TSTZRANGE --Josh

Re: [BUGS] pg_ctl restart issue with relative paths

/pgsql-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

Re: [BUGS] BUG #6715: 9.2b2 psql \ir does not understand leading ../

] of Gurjeet's \ir patch which I reviewed, which had different behavior for pathname normalization than what got committed. Josh [1] http://archives.postgresql.org/message-id/BANLkTi=eW_nUH9195=9upqf7treg4uh...@mail.gmail.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make

[BUGS] spgist: palloc() negative size with smaller BLCKSZ

: 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 via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make

Re: [BUGS] BUG #6694: 9.2 beta 2 : psql commands \db and \db+ fail

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 via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http

Re: [BUGS] Tab completion of function arguments not working in all cases

like 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

Re: [BUGS] BUG #6672: Memory leaks in dumputils.c

is a patch to hopefully fix those two errors. I couldn't quite verify this fixes the OP's error messages, since checker-266 isn't done running make after several hours on this OS X machine. Josh dumputils_clang.diff Description: Binary data -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org

Re: [BUGS] BUG #6672: Memory leaks in dumputils.c

On Fri, Jun 1, 2012 at 11:38 AM, Anna Zaks zaks.a...@gmail.com 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 time

Re: [BUGS] BUG #6672: Memory leaks in dumputils.c

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.org) To make changes to your

Re: [BUGS] BUG #6624: Tab completion of identifier containing single backslash triggers warnings

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

Re: [BUGS] log_collector doesn't respond to reloads

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@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [BUGS] log_collector doesn't respond to reloads

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 Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription

[BUGS] 291 pg_toast_temp schemas?

%'; 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 subscription: http

Re: [BUGS] 291 pg_toast_temp schemas?

On 4/26/12 11:22 AM, Tom Lane wrote: Josh Berkus j...@agliodbs.com 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 with cleaning up

Re: [BUGS] 291 pg_toast_temp schemas?

On 4/26/12 3:48 PM, Tom Lane wrote: Josh Berkus j...@agliodbs.com 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.gita=commitdiffh=e43fb604d6db229d70d3101aa53348cc16a5473a I take it you're

[BUGS] log_collector doesn't respond to reloads

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

Re: [BUGS] log_collector doesn't respond to reloads

On 4/26/12 5:50 PM, Tom Lane wrote: Josh Berkus j...@agliodbs.com 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 blocking receipt of SIGHUP

Re: [BUGS] log_collector doesn't respond to reloads

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 PostgreSQL Experts Inc. http

Re: [BUGS] log_collector doesn't respond to reloads

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, something is preventing the logger from writing

Re: [BUGS] BUG #6609: pattern matching (version 8.2 or so...)

FROM my_table; By the way, LIKE in your example was incorrect: I think you wanted either 'SIMILAR TO' or the '~' operator depending on your needs. You might want to wrap the above SQL statement into a standalone function for cleanliness, if a schema redesign is not feasible. Josh -- Sent via

Re: [BUGS] BUG #6549: Wrong $PATH setting after installation

, ~/.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

Re: [BUGS] BUG #6524: lpermission denied to create extension ltree. Must be superuser to create this extension.

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 subscription: http://www.postgresql.org

Re: [BUGS] wCTE cannot be used to update parent inheritance table

On 1/28/12 5:27 PM, Tom Lane wrote: Josh Berkus j...@agliodbs.com 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, thanks for the report

Re: [BUGS] wCTE cannot be used to update parent inheritance table

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

Re: [BUGS] wCTE cannot be used to update parent inheritance table

, 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 a discussion to have on the pgsql-bugs list. Please take it to -hackers. -- Josh Berkus PostgreSQL Experts Inc. http

[BUGS] wCTE cannot be used to update parent inheritance table

-- 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

Re: [BUGS] BUG #6370: manual does not discuss transactional DDL

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

Re: [BUGS] 9.1.1 hot standby startup gets sigbus

! Josh -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] 9.1.1 hot standby startup gets sigbus

On Wed, Nov 30, 2011 at 10:50 PM, Tom Lane t...@sss.pgh.pa.us wrote: Josh Kupershmidt schmi...@gmail.com writes: On Wed, Nov 30, 2011 at 9:17 PM, Tom Lane t...@sss.pgh.pa.us wrote: It might be worth recompiling at -O0, first to see if that changes the behavior and second to see if it changes

[BUGS] 9.1.1 hot standby startup gets sigbus

. Or it could be some flakiness with the VM itself. But before I start blowing things away and trying to start from scratch, I figured I'd leave the machine alone for a bit in case this report is interesting and any more sleuthing would help. Josh pgdata# SELECT name, setting FROM pg_settings WHERE source

Re: [BUGS] 9.1.1 hot standby startup gets sigbus

On Wed, Nov 30, 2011 at 9:17 PM, Tom Lane t...@sss.pgh.pa.us 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

Re: [BUGS] BUG #6301: extra space in psql variable expansion

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

Re: [BUGS] BUG #6301: extra space in psql variable expansion

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 line SELECT 1; Josh -- Sent

Re: [BUGS] BUG #6301: extra space in psql variable expansion

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

Re: [BUGS] Cannot dump 8.4.8 database using later versions

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 PostgreSQL Experts Inc. http

[BUGS] Cannot dump 8.4.8 database using later versions

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

Re: [BUGS] Cannot dump 8.4.8 database using later versions

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 broke something. -- Josh Berkus

Re: [BUGS] Cannot dump 8.4.8 database using later versions

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

Re: [BUGS] BUG #5944: COPY FROM doesn't work with international characters

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 Experts Inc. http://pgexperts.com -- Sent via pgsql

Re: [BUGS] 'pg_ctl restart' confused about pathname to postgresql.conf

, 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

[BUGS] 'pg_ctl restart' confused about pathname to postgresql.conf

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

Re: [BUGS] psql's \copy incompatible with :variables

\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 mailing list (pgsql-bugs

Re: [BUGS] Problems with ENUM type manipulation in 9.1

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 list (pgsql-bugs

[BUGS] Broken selectivity with special inet operators

with a default estimate of 0.5. I've tried to locate the cause of this problem, but the code involved is rather convoluted and crusty, and I can't follow the logic. Help? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make

Re: [BUGS] Broken selectivity with special inet operators

On 9/21/11 1:56 PM, Tom Lane wrote: Josh Berkus j...@agliodbs.com 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 selectivity estimators at all. It's not so

Re: [BUGS] Broken selectivity with special inet operators

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@postgresql.org) To make changes to your

Re: [BUGS] Broken selectivity with special inet operators

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 PostgreSQL Experts Inc. http

Re: [BUGS] BUG #6164: Flashing dialog

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

[BUGS] psql's \copy incompatible with :variables

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

Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers

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 attached? Josh diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml

Re: [BUGS] BUG #5944: COPY FROM doesn't work with international characters

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. http

[BUGS] psql crashes with bad history file in 9.0.3

a stack trace ... -- -- 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

Re: [BUGS] BUG #5921: pg_dump asks for password

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

Re: [BUGS] BUG #5911: pg_notify() function only works when channel name is lower case

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 McDougallj...@schemaverse.com writes: When using the pg_notify

[BUGS] Mismapping of Mountain Time

? -- -- 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

Re: [BUGS] Mismapping of Mountain Time

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 that Ubuntu does not set $TZ

Re: [BUGS] Mismapping of Mountain Time

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 Experts Inc. http://www.pgexperts.com -- Sent via

Re: [BUGS] Multicolun index creation never completes on 9.0.1/solaris

. -- -- 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

Re: [BUGS] Multicolun index creation never completes on 9.0.1/solaris

*that*. -- -- 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

Re: [BUGS] Multicolun index creation never completes on 9.0.1/solaris

On 1/26/11 12:13 PM, Tom Lane wrote: Josh Berkus j...@agliodbs.com 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. Huh

[BUGS] Multicolun index creation never completes on 9.0.1/solaris

, 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

Re: [BUGS] Multicolun index creation never completes on 9.0.1/solaris

On 1/25/11 1:21 PM, Tom Lane wrote: Josh Berkus j...@agliodbs.com 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 turned

Re: [BUGS] Multicolun index creation never completes on 9.0.1/solaris

. -- -- 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

Re: [BUGS] BUG #5814: documentation bug

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/createuser.sgml index

Re: [BUGS] What happened to SSL_CIPHERS?

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. http://www.pgexperts.com -- Sent via pgsql-bugs

Re: [BUGS] What happened to SSL_CIPHERS?

if PostgreSQL was built with SSL support). -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes

[BUGS] BUG #5732: parsing of: WHERE mycol=123AND ...

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 noticed

Re: [BUGS] BUG #5732: parsing of: WHERE mycol=123AND ...

On Thu, Oct 28, 2010 at 8:01 PM, Tom Lane t...@sss.pgh.pa.us wrote: Josh Kupershmidt schmi...@gmail.com 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 with AND or OR.  Any situation

Re: [BUGS] BUG #5732: parsing of: WHERE mycol=123AND ...

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 -- Sent via pgsql-bugs

[BUGS] What happened to SSL_CIPHERS?

: 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. http

Re: [BUGS] Unable to create serial column even with permissions

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? -- -- Josh Berkus

[BUGS] Unable to create serial column even with permissions

). -- -- Josh Berkus - Josh Berkus PostgreSQL Experts Inc. CEO database professionals josh.ber...@pgexperts.com www.pgexperts.com 1-888-743-9778 x.508 San Francisco

Re: [HACKERS] Drop one-argument string_agg? (was Re: [BUGS] string_agg delimiter having no effect with order by)

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 your subscription

Re: [HACKERS] Drop one-argument string_agg? (was Re: [BUGS] string_agg delimiter having no effect with order by)

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. http://www.pgexperts.com -- Sent via pgsql

Re: [HACKERS] Re: Drop one-argument string_agg? (was Re: [BUGS] string_agg delimiter having no effect with order by)

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 make changes

[BUGS] auto-explain does not work with JSON csvlog

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. -- -- Josh

Re: [BUGS] [TESTERS] Location of certs -Windows 7 SSL mode?

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. -- -- Josh Berkus

[BUGS] local_preload_libraries filenames converted to lowercase

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

Re: [BUGS] local_preload_libraries filenames converted to lowercase

is the answer, given. Hmmm are double-quotes respected in postgresql.conf, though? Need testing. -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql

Re: [BUGS] Re: regexp_matches illegally restricts rows -- just a documentation issue?

to restrict the number of rows output. A subselect in the target list does not do so. However, that's completely another discussion. --Josh Berkus -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] regexp_matches illegally restricts rows

Severity: major (data loss) Versions Tested: 8.4.2, 9.0 HEAD Test Case: create table regex_test ( id serial not null primary key, myname text ); insert into regex_test ( myname ) values ( 'josh'),('joe'),('mary'),('stephen'), ('jose'), ('kelley'),('alejandro'); select id, regexp_matches(myname

[BUGS] Re: regexp_matches illegally restricts rows -- just a documentation issue?

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 rows, 3 of which have an empty array or a NULL in the 2nd column. Just

[BUGS] Error when lock conflict on REPLACE function

should have succeeded. Or it should have given a user-friendly error message. Opinions? --Josh Berkus -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] PD_ALL_VISIBLE flag error on 9.0 alpha 4

That's better, I was worried you'd gone all complimentary on me. grinNever fear that! Was that setting originally part of your design for HS? If so, why did you back off from it? --Josh -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription

  1   2   3   >