Re: [BUGS] 8.0: Absolute path required for INITDB?

rt, because INITDB for Sunday's CVS would not run without the -L option. -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [BUGS] 8.0: Absolute path required for INITDB?

/pg80b I did not move the tree. I will drop the data directory and re-run it so I can cut and paste the error this afternoon. -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [BUGS] 8.0: Absolute path required for INITDB?

e invocation option -L. [EMAIL PROTECTED]:/usr/local/pg80b/bin> I don't recall having this issue with 7.4. -- -Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please se

[BUGS] Garbage characters for \d table?

the server. Frankly, the circumstances are peculiar enough that I don't expect you to do anything about this bug report; instead I'm filing it in case any related problems crop up with 7.4's PSQL. And, yes, I tried re-connecting in case this was somehow line noise. -- __Aglio Da

Re: [BUGS] Garbage characters for \d table?

seems like, in PSQL, the use of non-ASCII characters should require quoted identifiers, but apparently not? -- __Aglio Database Solutions___ Josh BerkusConsultant [EMAIL PROTECTED]www.agliodbs.com Ph: 415-752-2500Fax: 415-752-2387 2166 Haye

[BUGS] Backward compatibility issue with 8.0b1

# \d cases ERROR: column "reltablespace" does not exist jwnet_test=# I thought that we were going to be better about backward compatibility in this version? -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)---

[BUGS] TOAST error in 7.4.2 on frequently truncated tables

only reference to the error I can find is for CLUSTER, which is confusing because none of the tables involved are clustered. Is this related to the index problem fixed in 7.4.x? -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)-

Re: [BUGS] TOAST error in 7.4.2 on frequently truncated tables

er it. Any workaround to fix? > I'm quite sure you couldn't get this error from anything except CLUSTER > or TRUNCATE in 7.4 though. Seems like your client-side code is in error > to be fingering a plain SELECT as the cause. Yeah, well, I can't get the client to install

Re: [BUGS] TOAST error in 7.4.2 on frequently truncated tables

problem with the data transfer.Maybe re-create the table? -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html

Re: [BUGS] TOAST error in 7.4.2 on frequently truncated tables

Tom, > Yeah, I think you're stuck with doing that. BTW, this is a pretty nasty error, although apparently infrequent give the lack of list e-mails. Can we fix it for 7.4 series? -- Josh Berkus Aglio Database Solutions San Francisco ---(end of b

[BUGS] Money type not gone?

Guys, Pardon me if this is redundant, but I've just noticed that the MONEY type still exists in 8.0b2.Didn't we say that we were getting rid of it? -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TI

Re: [BUGS] Money type not gone?

s get rid of it and replace it with a DOMAIN of NUMERIC. -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Re: [BUGS] Money type not gone?

.07m^3 But you can't reasonably: 10USD == 6.25UKL ... because that would require a query to money.yahoo.com to establish. -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 6: Have you sea

Re: [BUGS] SELECT FOR UPDATE and LIMIT 1 behave oddly

ny easy way to query "give me the first row which is not locked"?If I tie pg_locks to a query, will I get wierd effects? Just musing -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 1: s

Re: [BUGS] SELECT FOR UPDATE and LIMIT 1 behave oddly

nd-lock were a single statement, how would a race condition result? How could I test for it? -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings

[BUGS] Wierd results of math -- old bug I hope

gcc (GCC) 3.3.3 (SuSE Linux) (1 row) webmergers=# select 3000::NUMERIC*1024*1024; ?column? 3145728000 (1 row) webmergers=# select 3000*1024*1024; ?column? - -1149239296 (1 row) -- __Aglio Database Solutions___ Josh BerkusConsultant [

[BUGS] Inconsistent behavior with AGE()

TIMESTAMP); age 9 mons 27 days 11:17:19.889547 (1 row) -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your

Re: [BUGS] Inconsistent behavior with AGE()

robably don't need to change it. --Josh -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings

[BUGS] could not find /usr/local/timezone

I missing a package? -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

Re: [BUGS] could not find /usr/local/timezone

machine). So there's > something awfully odd here. That's postmaster's feedback on startup. Here's a clue: when I tried to enable automated log rotation (using the default filenaming scheme) I got the same error but it was fatal. Let me know if you want a trace. -- --J

Re: [BUGS] could not find /usr/local/timezone

Tom, > Please. Also, what nondefault configuration or postgresql.conf settings > are you using? Will have to get the trace tommorrow. Config options are --with-perl and --with-odbc -- Josh Berkus Aglio Database Solutions San Francisco ---(end of bro

Re: [BUGS] could not find /usr/local/timezone

Tom, > Please. Also, what nondefault configuration or postgresql.conf settings > are you using? Sorry for delay. Attached. And --with-perl --with-odbc -- --Josh Josh Berkus Aglio Database Solutions San Francisco gentoobug.gz Description: GNU Zip compresse

Re: [BUGS] [pgsql-bugs] Daily digest v1.1281 (14 messages)

n -- maybe somebody could add it to the FAQ. The reason it comes up often is that the "log" example is in our docs. Since it doesn't work as expected, I think we need to patch the docs. H ... would it be possible for the rule to call currval() instead of NEW.i

Re: [BUGS] [pgsql-bugs] Daily digest v1.1282 (5 messages)

fficient join type. If you need to update rows in a specific order, then write a script and use a loop. -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings

Re: [BUGS] could not find /usr/local/timezone

Dunno how that could make PG lose the libdir, though. Will send you the full config.log when I'm back in my office and can retrieve it. --Josh -- __Aglio Database Solutions___ Josh BerkusConsultant [EMAIL PROTECTED]www.agliodbs.com Ph: 415-752-2

Re: [BUGS] could not find /usr/local/timezone

ore, though. H ... did I maybe do hardlinks instead of symlinks? Better check. The mount points to a SAN filesystem. --Josh -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 8: explain analyze is your friend

Re: [BUGS] could not find /usr/local/timezone

Notes, I would think: -- Symlinking the PostgreSQL binaries may cause problems with PostgreSQL locating libraries and files, due to changes to make moving Postgres directories easier. It is recommended that you use --exec-prefix when compiling if you think you will need symlinks. -- --Josh Jo

Re: [BUGS] SELECT FOR UPDATE and LIMIT 1 behave oddly

? I > realize such a case is rare. Should we emit a warning when it happens? Well, limit+for update can be useful under some circumstances, as long as you understand its limitations.We found a workaround. So I'd oppose disallowing it. -- Josh Berkus Aglio Database S

Re: [BUGS] SELECT FOR UPDATE and LIMIT 1 behave oddly

st row not already locked for update".Then added some code on the client end for error handling, like race conditions and no rows being returned, both of which happen in production. -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of b

[BUGS] a question about the installation

did you run configure before running gmake? Please post: 1) How you obtained 8.0b4 and in in what format. 2) what platform you are on, and what exact version 3) your version of gcc 4) the /configure options and the gmake command you sent. 5) the full error output of the failed build. -- Josh

Re: [BUGS] [pgsql-bugs] pg_dumpall (7.3) 'public' schema bug

tgreSQL, they are "replaced" on a new migration server. pg_dump isn't capable of working around this, nor should it be. Search the archives of -Hackers mailing list for this issue; a few workarounds were suggested. -- Josh Berkus Aglio Database Solutions San Francisco --

[BUGS] Wrong version of INIT script in postgresql-7.3.8-3PGDG.i686.rpm

d with the postgresql-7.3.8-3PGDG.i686.rpm includes the following lines: # PGVERSION is: PGVERSION=7.4 This causes PostgreSQL not to start after the upgrade. It needs to be fixed to: # PGVERSION is: PGVERSION=7.3 --Josh -- __Aglio Database Solutions___ Josh Berkus

Re: [BUGS] Wrong version of INIT script in postgresql-7.3.8-3PGDG.i686.rpm

Tom, > Devrim fixed that several days ago, I thought. When did you pull down the > RPM, and from which mirror? Aha, it's about 10 days old. That explains it. --Josh -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end o

Re: [BUGS] concat fails 'sometimes' on empty colums in select

Stefan, > To simplify this operation you could create an operator that does > the coalesce for you. ÂThis has come up recently; search the list > archives for examples. Actually, it's on General Bits: http://www.varlena.com/varlena/GeneralBits/84.php -- Josh Berkus Aglio Database

Re: [BUGS] [pgsql-bugs] Checkpoints occur too frequently

in pg_settings, too. But this is strictly a numeral. -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

[BUGS] config option --with-pgport does not update postgresql.conf

Folks, Summary: --with-pgport option does not update postgresql.conf Severity: trivial Version: 8.0rc1 Platform: SuSE Linux 9.2, Celeron 1800mhz laptop Description: On a lark, I tried compiling RC1 using --with-pgport=5480, since I'm still using 7.4 on this machine as well. Once I finished

Re: [BUGS] [pgsql-bugs] Daily digest v1.1341 (25 messages)

n enabling access to specific ports -- particularly 5432. -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

[BUGS] Error in 8.0 rc5 with repeat calls to array operator

rt affects this, but since we're 24 hours from wrap, I thought I should raise this issue ASAP. -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

Re: [BUGS] Error in 8.0 rc5 with repeat calls to array operator

Folks, > I'm finding an issue I thought was fixed with RC2, which is affecting my > ability to use arrays in RC5: Oh, this may be a bug specifically in INTARRAY; that module is installed. -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---

Re: [BUGS] [pgsql-bugs] Daily digest v1.1346 (21 messages)

all which autmatically "protects" some ports. Please see the service pack documentation, and make sure that you have opened port 5432, and re-test. -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 2:

[BUGS] Inconsistent behavior with TIMESTAMP WITHOUT and epoch

MT. This is inconsistent; it should do either local time or GMT for both. --Josh Berkus P.S. if anyone is wondering why I'm doing epoch with timestamp-no-tz it's for a calendaring application which exists on 2 servers in two different time zones, and all I really

Re: [BUGS] Inconsistent behavior with TIMESTAMP WITHOUT and epoch

estamps to be location-agnostic (such as this one, with servers on east and west coasts, and some talk about London), you want your timestamps stored as GMT. However, having changed it in 7.3, I agree that we'll just cause trouble changing it back. -- Josh Berkus A

Re: [BUGS] Inconsistent behavior with TIMESTAMP WITHOUT and epoch

ark-on-the-calendar (what I'm dealing with), and that my trouble stems from trying to coerce the first into the second. Maybe it's time to hack a datatype ... -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 8: explain analyze is your friend

[BUGS] Index scans for unique index not visible in stats

blic | unq_test|0 | 0 | 0 | 0 | 5 | 0 | 0 -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 3: if posting/reading throug

Re: [BUGS] [pgsql-bugs] Daily digest v1.1387 (8 messages)

e HAVING clause. Personally, I've always felt that the SQL committee made a mistake in having aggregates of no rows produce a single null output row; it leads to wierdness like this here. Hopefully someone can back that up with an ANSI-SQL reference ... -- Josh Berku

Re: [BUGS] BUG #1552: massive performance hit between 7.4 and 8.0.1

Brian, They PGSQL-PERFORMANCE list is really the appropriate place for performance issues like yours. Subscribe? http://www.postgresql.org/community/lists -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast

Re: [BUGS] BUG #1552: massive performance hit between 7.4 and 8.0.1

1/2 of the primary postgresql programmers read the performance list. -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings

[BUGS] pg_ctl inappropriately timing out?

Is there some way for pg_ctl to intelligently detect this situation? To set a timeout value for pg_ctl via a command-line option? -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 8: explain analyze is your friend

Re: [BUGS] pg_ctl inappropriately timing out?

ERM and SIGKILL > when init wants to shut you down ... Well, I can run an actual timer if you like. But it's definitely more than 20 seconds. And we're using the default bgwriter config, perhaps I should set it to 0? -- Josh Berkus Aglio Database Solutions San Francisco

[BUGS] PSQL commands not backwards-compatible

" does not exist This is from CVS, the day before the beta release. Ignore me if it's already been fixed. -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 9: In versions below 8.0, the

Re: [BUGS] PSQL commands not backwards-compatible

mething in the release notes: WARNING: 8.1's "psql" is not completely backwards-compatible with previous versions of PostgreSQL. --Josh -- __Aglio Database Solutions___ Josh Berkus Consultant josh@agliodbs.comwww.agliodbs.com Ph: 415-752-2500

Re: [BUGS] PSQL commands not backwards-compatible

nt version of PostgreSQL." -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 6: explain analyze is your friend

[BUGS] plpgsql TEMP table issue not fixed in 8.1?

runs_run_id_seq'), $1 , $2 [ $3 ] )" PL/pgSQL function "generate_test_series" line 67 at SQL statement ERROR: relation with OID 16607 does not exist This is CVS as of a week ago. -- --Josh Josh Berkus Aglio Database Solutions San Francisco -

[BUGS] ALTERed DEFAULTS not visible to PL/pgSQL cached plans

gtest; id | name | is_true ++- 1 | Before ALTER | 2 | Look, its null | t 3 | Now its true. | t -- --Josh Josh Berkus Aglio Database Solutions San Francisco create table bugtest ( id serial not null primary key, name text not null unique ); creat

[BUGS] psql: SELECT INTO with FETCH_COUNT enabled

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

[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

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

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

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

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

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.

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

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

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

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

[BUGS] Unable to create serial column even with permissions

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

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

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

[BUGS] 9.0 Bug: cannot build against python3.1, with two versions of python in the environment

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

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

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

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

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

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

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

Re: [BUGS] What happened to SSL_CIPHERS?

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

Re: [BUGS] What happened to SSL_CIPHERS?

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

Re: [BUGS] BUG #5814: documentation bug

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

[BUGS] Mismapping of Mountain Time

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

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 t

Re: [BUGS] Mismapping of Mountain Time

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

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

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

[BUGS] psql crashes with bad history file in 9.0.3

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

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

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.

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

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

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

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

Re: [BUGS] BUG #6164: Flashing dialog

-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

[BUGS] Broken selectivity with special inet operators

'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

Re: [BUGS] Broken selectivity with special inet operators

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

Re: [BUGS] Broken selectivity with special inet operators

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@

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

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

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

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

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

"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

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

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

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

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

[BUGS] Cannot dump 8.4.8 database using later versions

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

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 br

<    1   2   3   >