On 18/12/2009 4:00 PM, Dave Page wrote:
On Fri, Dec 18, 2009 at 1:59 AM, Craig Ringer
wrote:
On 17/12/2009 6:10 PM, Vincent Pinto wrote:
The following bug has been logged online:
Bug reference: 5248
Logged by: Vincent Pinto
Email address: vincent_pi...@mentor.com
On 18/12/2009 4:15 PM, Dave Page wrote:
On Fri, Dec 18, 2009 at 8:01 AM, Craig Ringer
wrote:
On 18/12/2009 4:00 PM, Dave Page wrote:
On Fri, Dec 18, 2009 at 1:59 AM, Craig Ringer
wrote:
On 17/12/2009 6:10 PM, Vincent Pinto wrote:
The following bug has been logged online:
Bug
ng if it there's any sign of a
missing required library.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
NTAINED TEST CASE - with ".sql"
database dump or creation script, plus complete and compilable
stand-alone Java code to demonstrate the problem. If you can't hand out
your data, write something that generates dummy data that'll reproduce
the problem.
Read the logs, take note of
backend is supposed to
be somewhat safe.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
nd also
>> tried C:\Program Files\PostgreSQL\8.4, problem is probably not with
>> install path.
>
> try a path without a space in it. I put mine on D:\Postgresql_84\
That _really_ shouldn't make a difference - and if it does, it's a bug.
I've had no issues wi
ce WHERE c.relkind IN
('r', 'v', 'S');
\o
Please attach "output.txt" rather than copying and pasting, so that line
wrapping is preserved.
--
Craig Ringer
--
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/01/2010 6:18 PM, Goodomens wrote:
Craig Ringer
I come from Shanghai of China,my english is not well,sorry.
>Is this the output of psql's `\dp' command? If so, where are the actual
>privelege rows - did you delete them, or is the output you pasted
>actually EXACTLY wh
figuring shared memory.
You need to lower shared_buffers, lower max_connections, and/or increase
your kernel's shared memory limit.
With 803 connections, I'm guessing you have one connection per client.
Avoid this if possible - use a server-side connection pooler.
--
Craig Ringe
attribute at ordinal
position 2.
I'm pretty certain that's not a bug.
It's certainly a feature limitation of PostgreSQL, but it's working as
(currently) designed. You're expected to reload any functions after
dropping columns of tables.
I've seen this discusssed recen
e a look at the archives.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
l.org/wiki/Guide_to_reporting_problems
and try to explain your problem in a bit more detail.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
able so, that
> message should not appear?
CREATE INDEX (without CONCURRENTLY) takes a lock on the table that
blocks INSERT/UPDATE/DELETE (but not SELECT), yes.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
olumn' diagrams are open
Details:
if you open two 'add column' dialogs and will in the second and click ok
then try to fill in the second and click ok the program crashes.
I think you might have the wrong program. Or do you mean PgAdmin or one
of the other related tools?
--
Craig
on the JDBC list about this.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ause of the problem you report, but: Most databases,
and certainly PostgreSQL, perform poorly on RAID 5. In particular,
PostgreSQL really doesn't like having the WAL stored on RAID 5, but
really you're much better off using RAID 10 for all your
database-related storage if you can.
--
Craig
George wrote:
> The following bug has been logged online:
> My project is migrating from Oracle to postgresql,can you help me ?
This is a bug report form.
Perhaps you were looking for the pgsql-general mailing list?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsq
resql.org/support/professional_support
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
of a great many providers listed here:
http://www.postgresql.org/support/professional_support_asia
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
a bug on the postgresql package in Ubuntu's
Launchpad. It's an issue with the postgresql packaging for Ubuntu and
can't really be resolved by the upstream PostgreSQL project.
See:
https://launchpad.net/ubuntu/+source/postgresql-8.3/+bugs
--
Craig Ringer
--
Sent via pgsql-bugs
able-shared being specified
> and as far as i could spot and go through other makefiles i couldn't
> notice any of the rules being used outside unless shared libraries are
> used.
Perhaps offering an option to build *just* libpq, and do that
statically, would be useful to some.
--
Cr
m not saying the crash doesn't need fixing, _but_: why not use
statement_timeout instead?
Are you trying to get rid of idle backends, too, or backends that're
just transferring data to the client?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
w count would always be 1, and the value returned would
be the "real" row count.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
tools
and see if the server's actually DOING anything. You'll probably find
it's busy with disk I/O and not really stalled at all.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
parenthesis.
Details:
Your issue is the different behaviour between the `library' and `pgsql'
users?
Do they have a different search_path setting?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
ntime library. It's installed
by a bundled installer provided by Microsoft.
Can you download the Microsoft Visual C++ 8 (2005) runtime redist from
Microsoft directly and try installing it?
http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displa
; sometimes I get messages from -general in rather wacky orders,
with replies before originals etc.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
27;s what -bugs is anyway; it's just
less visibly so. Dups and non-bugs are easily closed by the same folks
who're active on -bugs triaging here.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
T=7654 psql -U postgres postgres -c
'show client_encoding;'
client_encoding
-----
WIN1250
(1 row)
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ll be down !
Error message?
Does this happen with a blank database, or just with your `db' ?
If you pg_dump to a file instead of piping to psql, does that work?
If you then restore that file using psql, does that work?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgres
t spam you. See:
http://developer.apple.com/programs/register/
(click "Get Started")
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
g the "ps" command - "ps -ef" or "ps aux" depending, I
don't remember which flavour Mac OS X understands - passed through "|
grep psql".
I have the developer tools installed - but I think only because I needed them
installed to install something ages
On 13/04/10 21:16, Ben Madin wrote:
G'day Craig, thanks for your reply.
Please disregard my follow-up. I hadn't seen Tom's reply that he was
able to reproduce the issue. There's no need for you to collect a
backtrace now :-)
--
Craig Ringer
--
Sent via pgsql-bugs mail
s definitely applying a different rule to the interpretation
of unqualified "character" in RETURNS TABLE functions to what it applies
to CREATE TABLE, and is getting pretty darn confused between its
character types in general.
I'd certainly call this a bug, if not a couple of different bugs. Er,
help?!?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
a bug here, if _tables_ can be created with
character(1) fields containing three- or four-character strings.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 15/04/2010 10:25 AM, Tom Lane wrote:
Craig Ringer writes:
So - I do think there's a bug here, if _tables_ can be created with
character(1) fields containing three- or four-character strings.
[ shrug... ] If you can demonstrate such a behavior, I'd agree it's a
bug, but
see the postgres account there and can reset its password if
required.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
uests, IMO any tracker
would *have* to allow triage folks to place bugs in a NEEDINFO / INVALID
/ NOTABUG state, and to report on bugs with no activity in >n days/weeks
so this can be done quickly and easily for non-responsive reporters.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.
firmed bug in 3rd party software, forwarded
Pretty much any existing tracker can do this, but especially if you want
a little bit of reporting ... is it really worth building a whole new
one for the job?
IMO all the above would be pretty handy, particularly when people are
looking for things later
ce you can follow these instructions:
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
and get a backtrace of the crash?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
u
ran leading up to this error, the exact OS and distro version, your
version of gcc and make, etc.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
it's just a mattter of adding appropriate variable
substitutions for the install lines of those files. I'll look at it in
the morning (it's late here) if nobody beats me to it - this is probably
something my meagre skills are actually up to ;-)
--
Craig Ringer
--
Sent via pgsql-bug
command in cmd.exe:
chcp
and, agan, reporting the output.
Also, what was the exact error message given when the install failed? (
A screenshot wouldn't hurt ).
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
delete the `postgres'
user account. Do so through Control Panel -> Administrative Tools ->
Computer Management.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
occur if a GIST index is present on
`po_message.message' instead of a GIST index, or if no index is present
at all. It only arises when the % operator is used.
--
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
he support for actually executing
it was written.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
l enough to help you.
Note: I do not speak for the PostgreSQL team, I'm just a user trying to
help out.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
o
record a trace of a successful initdb and of a failed one, you'd have a
bit more information about what is actually happening to work with.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged online:
Bug reference: 5468
Logged by: Craig Ringer
Email address: cr...@postnewspapers.com.au
PostgreSQL version: 8.4
Operating system: Ubuntu 10.04, but affects all
Description:Pg doesn't send accepted root CA list to client d
On 21/05/2010 10:35 PM, Magnus Hagander wrote:
On Fri, May 21, 2010 at 7:52 AM, Craig Ringer
wrote:
The following bug has been logged online:
Bug reference: 5468
Logged by: Craig Ringer
Email address: cr...@postnewspapers.com.au
PostgreSQL version: 8.4
Operating system
On 22/05/10 12:01, Craig Ringer wrote:
On 21/05/2010 10:35 PM, Magnus Hagander wrote:
>>
Unfortunately, I don't think this is something we can fix as a bugfix
- it'll be a pretty clear change of behaviour, so I think it's
something we will need to push back for a full rele
On 24/05/10 00:58, Tom Lane wrote:
Craig Ringer writes:
+ SSL_CTX_set_client_CA_list( SSL_context,
SSL_load_client_CA_file(ROOT_CERT_FILE) );
Hmm, what about failures? If we're loading the root cert file a second
time, it's possible that the user just changed it an
On 25/05/10 23:48, Tom Lane wrote:
Craig Ringer writes:
Bug 5245 is not the same issue. They're talking about the server not
sending the full certificate chain for the cert that identifies the
server (server.crt). It's nothing to do with client certificates.
Without the full chain,
On 26/05/10 07:37, Tom Lane wrote:
Craig Ringer writes:
I do *not* have the CA cert concatenated onto server.crt. I'll have to
see if that works, because that's how it's usually done with OpenSSL.
Hmm. That case doesn't work for me; what does work is including the
inte
ins of CA certs.
Yes, and patch the server to send the list of trusted CAs to the client
during client certificate negotiaton to fix #5468 .
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.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 26/05/10 09:59, Craig Ringer wrote:
> On 26/05/10 09:35, Tom Lane wrote:
>
>> I am now of the opinion that bug #5245 is in fact an exact dup of
>> bug #5468. The previous reporter was jumping to conclusions about what
>> his problem was: it was not that the server d
On 26/05/10 10:16, Tom Lane wrote:
> Craig Ringer writes:
>> You are confusing these two unrelated phases of SSL negotiation.
>
> No, I don't think so.
http://www.cgisecurity.com/owasp/html/ch07s04.html
See in the second part, the new entry #5 "client request"
(
uilt-in usage/help:
http://www.postnewspapers.com.au/~craig/PgClientCertDemo.jar
sources and README:
http://www.postnewspapers.com.au/~craig/PgClientCertDemo.zip
Run the jar as:
java -jar PgClientCertDemo.jar
for help.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
--
Sent v
to put it all together and you'll have
something you can play with, watch chat on the network, etc.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
icates, a detailed log of test case setup, the test
programs, logs of test output along with explanation of those logs, etc.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to y
On 27/05/10 10:05, Tom Lane wrote:
Craig Ringer writes:
See the self-contained test case here:
http://www.postnewspapers.com.au/~craig/testcase.zip
Thanks for posting that; it makes it a lot easier to experiment with the
behavior of the Java software stack.
I've applied your patch
can enlighten us; I've jumped to the
thread for #5245 for that purpose.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
isplaylang=en
) separately, are you then able to install Pg?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
#x27;),
('b','20100430 00')
) AS x(a,b)) AS y;
... which is why your example is unsafe, and even if it appears to work
on other databases it is buggy. Instead, write:
insert into test_insert
(col1, col2)
select distinct
'b',
CAST('2010-04-30 00:00:00' AS tim
uarantee input formatting consistency, so it's safe for you so long as
you stick very closely to timestamp formatting specifics, but I'm sure
you can see that a database's behaviour depending on the formatting of
timestamps is probably not something that most people with most apps
ent in the system
that the SELECT part of the INSERT INTO ... SELECT ... could
determine the SELECT output columns type by looking at the INSERT
target table definition
I'd say that'd be a ghastly "solution". It'd change the meaning of the
SELECT based on the
See:
http://www.depesz.com/index.php/2008/05/05/error-operator-does-not-exist-integer-text-how-to-fix-it/
http://petereisentraut.blogspot.com/2008/03/readding-implicit-casts-in-postgresql.html
http://wiki.postgresql.org/images/d/d1/Pg83-implicit-casts.sql
--
Craig Ringer
--
Sent via pgsql-bu
you VACUUM regularly / is autovacuum enabled?
See: http://www.postgresql.org/docs/8.3/interactive/routine-vacuuming.html
See:
http://wiki.postgresql.org/wiki/Introduction_to_VACUUM%2C_ANALYZE%2C_EXPLAIN%2C_and_COUNT
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To ma
They don't seem to have these issues.
Perhaps a FAQ entry would be a good idea in the mean time, though. Let
me see if I can put something together.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 09/06/10 15:47, Dave Page wrote:
> On Wed, Jun 9, 2010 at 4:58 AM, Craig Ringer
> wrote:
>
>> Really, the installer on Windows needs to stash the password in an
>> admin-only-readable registry key, read it from there on install, and test to
>> make sure it works. I
On 09/06/10 16:29, Dave Page wrote:
> On Wed, Jun 9, 2010 at 8:56 AM, Craig Ringer
> wrote:
>
>> Only because the PostgreSQL system user account password is coupled to
>> the account of the "postgres" user in the PostgreSQL database cluster
>> (right?). I&
asking for
help on the lists suggests that it's confusing to some. An enhancement
in the installer could remove the need for that.
It's nothing more than a suggestion, I just hope you'll consider
examining this part of the process in light of some of the questions
that turn up o
if the service account password management can be made
transparent in some way, which it seems it can't really) then the
current way is pretty good once you really dig down and compare it to
the alternatives.
Once again, thanks for taking the time to go through it.
--
Craig Ringer
ve tools, THEN re-install.
Alternately, just re-install with the old password then log in to
PostgreSQL as the "postgres" user and change the postgres user's password.
This confusion arises because there are two "postgres" users - a system
user, and database user. Mo
e your packages FROM?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
#x27;t cause problems in this case, it
can. If in doubt, type "cd" then enter before running an install command
so you go to your home directory.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
om your post? Or are you just asking for help with a query?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
so I haven't been too worried about libpq's client cert handling.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 8/07/2010 6:31 PM, Magnus Hagander wrote:
On Thu, Jul 8, 2010 at 03:10, Craig Ringer wrote:
IIRC on Windows client certificates live in
%APPDATA%\.postgresql\
That's a typo, it should be %APPDATA%\postgresql\ (no leading period).
You're quite right. Sorry - I thoug
have posted.
Please only report bugs in the bug report form.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
.
I wonder if there's any way to have the bug report form de-duplicate
posts based on similar/identical text in sequential submissions.
I just replied to this as #5546, only to read a bit further through my
mail queue and find out that others have already addressed it as #5547.
--
Craig R
re
that the information you collect is useful. See the instructions above.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
er for PostgreSQL. As you haven't
mentioned where you got PHP from or much else, it's hard to help you
much. Try posting to a PHP forum with a bit more detail, or try on
http://serverfault.com/ .
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
was up
to when it crashed. There are some instructions on how to get a stack
trace on the wiki:
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs maili
x27;t
install a 64-bit ODBC driver yet, and anyway you'd need to configure the
32-bit one for access by any 32-bit apps.
--
Craig Ringer
Tech-related writing at http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscrip
indows. I haven't seen many reports either way here,
but perhaps there's more discussion of it on the EnterpriseDB web
forums: http://forums.enterprisedb.com
--
Craig Ringer
Tech-related writing at http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
#A_bug_I.27m_encountering_is_fixed_in_a_newer_minor_release_of_PostgreSQL.2C_but_I_don.27t_want_to_upgrade._Can_I_get_a_patch_for_just_this_issue.3F
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
c, just collect the
logs up and wait for people to ask you to send them to them by private
email. Please send a copy to me, as I've dealt with encoding issues in
software (though not PostgreSQL) quite a bit.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To
ting your
error messages, or your locale files aren't the same as mine. I doubt
the latter; it seems almost impossible that just a few messages would be
converted to shift-JIS by accident in the Windows release only. So the
question now is where the messages are converted from UTF-8 t
re firewall on your system.
- If you have the same problem on a clean Windows 7 install, prior to
adding a virus scanner or other local software. I realise this might not
be practical for you to test, but it'd be useful for diagnostic purposes.
--
Craig Ringer
Tech-related writing at
em.
On 21/09/2010 1:53 PM, Roedy Green wrote:
On 2010-09-20 10:20 PM, Craig Ringer wrote:
On 21/09/2010 4:49 AM, Roedy Green wrote:
The following bug has been logged online:
Bug reference: 5667
Logged by: Roedy Green
Email address: roe...@mindprod.com
PostgreSQL versio
running a German build of Windows 7, with a localized name
for C:\Program Files . Given the name, you are also obviously running a
64-bit Windows 7 build. I can't help but wonder if the Pg installer is
looking for the non-localized path, though I thought Windows did some
path rewriting to work
- Write a Hibernate UserType (this is **trivial** to do) that translates
boolean to/from database short using the setInt() and getInt() JDBC
driver methods. Then use this on your boolean mappings.
- Write a custom PostgreSQL dialect for Hibernate that ignores
PostgreSQL's boolean support and
the close box? Or do you have to End Task it?
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
g. I don't know if the EnterpriseDB installer packages the .pdb
files (debug information) for PgAdmin III, though, and without that a
debugger on Windows is pretty useless. I'll have to check when I have
access to Windows once I'm home if nobody can confirm sooner.
--
Craig
e problem happen with any database? Or just one?
> All databases on all servers
>
> Can you browse the contents of databases, create databases, and perform
> all other tasks fine? Is it *just* SQL editing that's failing?
> All other operations appear to be OK - just SQL ed
on the list. I seem to remember that process monitor's
export format is MUCH less useful than it's live format, though, so I
don't know if it'll be much help.
Hopefully one of the EnterpriseDB folks will be able to look into what's
happening here, time permitting. They&
fixes to shared memory on windows since 8.3. Does 9.0
work better on your machine?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
e been plenty of problems with shared memory that seem to have been
fixed in 8.4 .
It would be a good idea to try 8.4 or 9.0 and see if you still have the
problem there. If you do, then we'll at least be working with a current
version when debugging/testing.
--
Craig R
27;re having, though.
--
Craig Ringer
Tech-related writing at http://soapyfrogs.blogspot.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
101 - 200 of 453 matches
Mail list logo
