res a valid client
> certificate
I think this indicates that pg_ctl is trying to connect to the
database just to see if it's running, but you have set it to require
SSL certificate on connections from localhost. Could that be so? If
so, try setting the requirement for certificates only o
On Wed, Aug 26, 2009 at 15:30, Tom Lane wrote:
> Magnus Hagander writes:
>> I think this indicates that pg_ctl is trying to connect to the
>> database just to see if it's running, but you have set it to require
>> SSL certificate on connections from localhost. Could
was broken recently, because it's been working. I'll
> ask the sysadmin team.
That's not maintained by the sysadmin team. You need to ask hub.org.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.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 Wed, Aug 26, 2009 at 15:57, Tom Lane wrote:
> Magnus Hagander writes:
>> But that will still fail if the user has set it up to require a client
>> certificate.
>
> But not till it gets to the pg_hba checks. We might need to have some
How would that be different from what
On Wed, Aug 26, 2009 at 22:47, Tom Lane wrote:
> Magnus Hagander writes:
>> On Wed, Aug 26, 2009 at 15:57, Tom Lane wrote:
>>> Magnus Hagander writes:
>>>> But that will still fail if the user has set it up to require a client
>>>> certificate.
>>
Is this solution fine or some fix is needed in code?
I think that qualifies as a workaround, but we need to find a proper
solution. If that takes an API change (the discussions about a "ping"
function), that's not going to be until 8.5 though.
--
Magnus Hagander
Me: http://www
_sqlca @ 42
>
Fix applied - exports.txt had a tab in it, instead of spaces, to
separate the field from the number.
Clearly we don't have a regression test that uses this function, or it
would've broken mingw buildfarm members. Should we have that?
--
Magnus Hagander
Me: http:/
2009/8/27 Tom Lane :
> Magnus Hagander writes:
>> Fix applied - exports.txt had a tab in it, instead of spaces, to
>> separate the field from the number.
>
> Hmm, maybe it would be better to fix whatever sed script is presuming
> the form of the whitespace? Because ot
a table
> there.
Yeah, there's some issues wrt how it's distributed to the different
servers. I *think* I fixed it so it wouldn't break from a simple
addition last time, but I can do the addition this time as well so I
can verify right away if it worked.
A simple field saying
On Thu, Aug 27, 2009 at 19:41, Tom Lane wrote:
> Magnus Hagander writes:
>> 2009/8/27 Tom Lane :
>>> Magnus Hagander writes:
>>>> Fix applied - exports.txt had a tab in it, instead of spaces, to
>>>> separate the field from the number.
>>>
&g
only thing you changed going
from 8.3 to 8.4? Or did you also upgrade something else on the system?
Do you use SSL for your connections?
Can you also try the latest 8.3 (8.3.7) to see if some backported fix
caused this?
And the usual question always applies - any firewall or antivirus on the serv
pg_stat_* are not directly affected by ANALYZE. They collect runtime
statistics about activity in the tables, ANALYZE collects statistics
about what's *in* the tables (primarily stored in pg_statistics, not
pg_stat_*).
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.
On Wed, Sep 2, 2009 at 06:25, Tom Lane wrote:
> Magnus Hagander writes:
>>> and when i try to recover them via an analyze; (on all tables on the
>>> database) the result is nothing...
>>> i have to exexute the analyze commands twice to compute the statistics
&
On Fri, Aug 28, 2009 at 15:38, Alvaro Herrera wrote:
> Magnus Hagander escribió:
>> On Fri, Aug 28, 2009 at 05:03, Alvaro Herrera
>> wrote:
>
>> > It would be good, but currently that list comes from a database that
>> > cannot handle external lists.
gt; and fails to found pg_autovacuum in pg_catalog.
>
> Please tell what should we use for that. Is there any patch available for
> that.
You need slony 2.0.3 in order for 8.4 to be supported. It's available
as a release candidate, IIRC.
--
Magnus Hagander
Me: http://www.hagander
stimate that more
> than one-third of those reports never show up.
They get processed in the moderator queue of -bugs along with all
other posts there... We're probably just back in the situation where
we need more moderators for it...
--
Magnus Hagander
Me: http://www.hagander.net/
W
#x27;t necessarily need a limit, we could accept
> arbitrarily long tokens. Although I guess we want to avoid simple
> denial-of-service attacks exhausting backend memory.
Yeah.
FWIW, the default max token size on Win2k is ~8Kb. In some service
pack and then in Win2003, it was increased to 12K
2009/10/13 Tom Lane :
> Heikki Linnakangas writes:
>> Magnus Hagander wrote:
>>> Actually, I found a note that said it's recommended to never increase
>>> it about 65535 - so perhaps we should put our limit at that instead od
>>> 32767?
>
>> Yea
p core depending
> on the contents of the not-allocated msg[0] array member.
>
> I will go and rewrite this function to look more like openssh's,
> on the assumption that their version is probably pretty well battle
> tested.
Yeah, that sounds like a reasonable thing to do.
--
more urgent than maybe a week
worst case, in which case someone else has to pick it up :-)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.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 Wed, Oct 21, 2009 at 15:34, Andrew Dunstan wrote:
>
> Magnus Hagander wrote:
>>
>> From a quick look, it looks fine to me. I don't have time to do a
>> complete check right now, but I'll do that as soon as I can and then
>> commit it - unless people
On Saturday, November 14, 2009, Tom Lane wrote:
> Magnus Hagander writes:
>> I've finally looked it over, and it still looks fine. I've cleaned up
>> some of the whitespace issues in the patch and applied it, including a
>> backpatch to 8.3 and a forward-patch
On Sat, Nov 14, 2009 at 18:12, Magnus Hagander wrote:
> On Saturday, November 14, 2009, Tom Lane wrote:
>> Magnus Hagander writes:
>>> I've finally looked it over, and it still looks fine. I've cleaned up
>>> some of the whitespace issues in the patch and
On Mon, Nov 16, 2009 at 06:23, Tom Lane wrote:
> Magnus Hagander writes:
>>> On Saturday, November 14, 2009, Tom Lane wrote:
>>>> Not 8.2?
>
>> Done.
>
> Buildfarm member narwhal seems to think it's not quite right in 8.2.
Drat.
So, the new API f
27;m not sure I understand what you mean, but I think you mean use the
certificate to authenticate to the database, and not just as an extra
step of validation? If so, it's already in PostgreSQL 8.4, and you
just need to upgrade.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: htt
2009/11/16 Tom Lane :
> Alvaro Herrera writes:
>> Magnus Hagander wrote:
>>> Which leads to the question - do we want to back out the
>>> patch, have 8.2 keep working on that, and having 8.2 fail in the few
>>> unusual scenarios we have now, or do we also bac
es them all to be scheduled on the
same CPU? (That's a part of the Windows scheduler, not PostgreSQL).
I guess it's also possible that PHP has some kind of mutex that makes
it run only one in parallel, but PostgreSQL doesn't. To prove that,
try running the comments through &quo
about this on
> the bug submission page? I asked for this before and Tom concurred,
> but I'm not aware that anything has been done about it. What do I
> have to do to make this happen?
Suggest the exact text? ;)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
specifically the part about symbols.
Which it certainly looks like :)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
On Wed, Dec 16, 2009 at 17:43, Alexey Luchko wrote:
> On 16-12-2009 17:45, Magnus Hagander wrote:
>>
>> If that is so, the OP should follow:
>>
>> http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
>>
>&
tp://developer.postgresql.org/pgdocs/postgres/app-psql.html#R2-APP-PSQL-CONNECTING
Yes, that is definitely supposed to work. It was intentionally added
in 8.3 and is very useful :-)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
uggest you upgrade.
However, that's just the shared memory problem. Which is a secondary
problem to the connection closed one, that prevents the system from
properly restarting after a failure.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent
Any chance you have a firewall or such intercepting the request? And
either rejecting it or showing a captive portal or something? Can you
download that URL in a webbrowser on the same machine?
/Magnus
On Tuesday, March 9, 2010, Helena Biander wrote:
>
> The following bug has been
using always DEVNULL, but back-branches need
> that too. I'll leave NULL_DEV as it is just in case it's used by 3rd
> party modules, but change the two uses of it to use DEVNULL.
Sounds good to me.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-l
inaries just because they have non-standard equipments.
>
> A patch attached. The name of "PGMODULEEXPORT" might be arguable.
I agree with this in principle, but won't this break every single
add-on module out there that supports Win32?
--
Magnus Hagander
Me: http://www.ha
On Tue, Apr 6, 2010 at 21:55, Tom Lane wrote:
> Magnus Hagander writes:
>> On Mon, Mar 29, 2010 at 11:47 AM, Takahiro Itagaki
>> wrote:
>>> A patch attached. The name of "PGMODULEEXPORT" might be arguable.
>
>> I agree with this in principle, but won
ID 1011) was terminated by signal 11:
>> Segmentation fault
>
> Oops! I guess that this happened because walrcv_disconnect() was called in
> WalRcvDie() even though libpqwalreceiver.so couldn't be loaded. The attached
> patch would fix the problem.
Applied, thanks.
--
Magnu
mitfest app is dang close to that already.
Let's not do that without thinking really careful about it. The
commitfest app is good at what it does precisely because it's designed
to do just that, and nothing more (or less). Twisting it into doing
other things may make things worse r
uing immediate stops
> or killing with -9 had been quite catastrophic and I could not start the DB
> afterwards. What would you suggest in this case?
kill -9 on a client will make the postmaster restart the whole
process, so yes, it's a very heavy operation.
--
Magnus Hagander
Me
/* (GMT+06:00) Almaty, Novosibirsk */
>
> Which is probably wrong.
Why? :-)
Windows makes no difference between Almaty and Novosibirsk in it's
listing. If we pick the Novosibirsk one by default, that will just
break Almaty. There's no real easy way for us to find the difference
On Wed, May 19, 2010 at 3:12 PM, Alvaro Herrera wrote:
> Excerpts from Magnus Hagander's message of mié may 19 15:03:25 -0400 2010:
>> On Wed, May 19, 2010 at 3:00 PM, Alvaro Herrera
>> wrote:
>> > Excerpts from Dmitry Funk's message of mié may 19 13:44:35
rs" local group.
>
> Please help me with this error.
Just use whatever tool you'd normally use to edit your users, for
example the Local Users and Groups mmc snapin.
//Magnus
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
uo got that from, because that's not PostgreSQL.
If you have postgres.exe files, which is the PostgreSQL backend exe,
then you need to check your logs (both eventlog and the pg_log
directory, depending on how it's configured) for error messagesn that
will in
and see if that helps (sometimes it's
enough to disable them for the pg processes, sometimes you need to
uninstall them completely).
If that doesn't help, search for LSPfix - it's a tool that can help you
fix it.
//Magnus
---(end of broad
t Tools (on your windows
CD) on pltcl.dll ("depends pltcl.dll" when in that directory) to see which file
it won't load.
//Magnus
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
pg_dump.exe dbname -U postgres -W -f dbname.sql < password.txt
>
> in 8.0.3 is work
>
> in 8.1.4 is not work need manual key in password.
The bug is in 8.0.3 (and <= 8.1.3 as well), fixed in the latest
versions. If you want to pass the password to pg_dump, use pgpass.
ice, and logging there
instead?
Do you run this from the commandline, or from inside another program?
Finally, you can try the initdb version at
http://www.hagander.net/pgsql/initdb_pgctl_restricted_user_8.1.4.zip.
It's the 8.1.4 initdb with the run-as-admin fixes from HEAD backpatched.
en fixed in the latest versions in both
the 8.0 and the 8.1 series. Upgrade to 8.0.8 or 8.1.4 and see if that
fixes it.
//Magnus
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
uot;America/Buenos_Aires"
>
> (no human touch the windows configuration or regional)
Interesting.
Does the file America\Buenos_Aires exist within your
PostgreSQL\share\timezone directory?
//Magnus
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
backpatched, and it's definitly not in a
released version).
If you don't need the stats, try turning off them - specifically the row
level stats - in postgresql.conf. Beware that turning these off will
disable autovacuum if you are using that one. but it's worth testing to
see if it s
ord
Sounds like you need to talk to whomever makes PostgresDAC. What you're
getting is a crash in the client side program, so the problem isn't in
the server - it's either in your program or in the PostgresDAC library.
//Magnus
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
code for
8.2. Any chance you can try the cvs snapshot version and see if the
problem exists there as well?
//Magnus
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
when I investigate "User Accounts" from the
> control panel, it doesn't exist there either. I cannot
> therefore log onto the account, nor delete the account. If I
> try to create an account with the same name, it tells me that
> one already exists.
Is thi
SQL install and log on to that
> account.
>
> I guess that the fact the account + username doesn't appear on the
> welcome screen is a security feature enabled by the postgreSQL
> install, or something similar. Maybe the documentaion/FAQ could be
> updated to mention this behaviour?
Not necessarily a security feature, but a convenience feature. Service
accounts are for services and not for logging on, so it's common
practice not to have them show up on the login screen.
//Magnus
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
are downloading the wrong
file - you'll want the ZIP archive at
http://www.postgresql.org/ftp/binary/v8.1.4/win32/.
//Magnus
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
v6 protocol is not installed
I've never seen any mention at all about this before. Do you have any
antivirus or firewall software on this machine? Especially firewall
software has a bad habit of breaking regular winsock operations, as
we've seen in many different cases...
Als
d this in some
way. (Offline ATM, so I can't dig out the link for you. But it's on
www.postgresql.org/docs, under FAQs)
//Magnus
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
;) failed: code 2,
> errno 2
> LOG: Windows fopen("backup_label","r") failed: code 2, errno 2
This is not a problem. It's just debugging code left-over from a
different issue. The messages will be removed before the release.
//Magnus
-
those files
> on the file system.
No. It's debugging output for a problem we had earlier, and will be
removed before release.
//Magnus
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose
exactly?
filemon is a kernel mode filter driver. So it's looking at kernel-only
datastructures. AFAIK, there is no way to see that from userspace.
//Magnus
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
> > The same problem exists in 8.1 too. See this thread
> > http://archives.postgresql.org/pgsql-bugs/2006-04/msg00177.php
> > Tom and Magnus tracked down a cause, but I don't think a
> fix was ever
> > implemented.
>
> Thomas seems to have two different
GetLastError() or errno, but pgunlink doesn't?
Ok, I've built a .EXE with this patch. It's compiled without pretty much
all other options, hope that still works :-) (Meaning no NLS, no
kerberos, no SSL etc)
Grab the exe from
http://www.hagander.net/download/postgr
_windows.html#3.1
> I don't have antivir, don't have firewall.
You were likely at the correct FAQ and the correct question, but too
early in it. Specifiaclly, the part about cygwin seems it could apply.
Either that, or some other DLL is hanging upon loading - ch
It seems to me that it's not been included in b3. Tom?
//Magnus
> -Original Message-
> From: Thomas H. [mailto:[EMAIL PROTECTED]
> Sent: den 8 november 2006 12:59
> To: Magnus Hagander
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #2712: could not fs
;ve tested in Swedish_Sweden,
which also crashes.
Note that this appears not to be index related at all, because during
this test there is only a standard btree index on "someint", and nothing
on the tsvector column.
//Magnus
> -Original Message-
> From: [EMAIL PROTECTED]
&
;s
> configuration at all.
It doesn't. And in my repro, I used the \i method to load tsearch2.sql,
and that also causes the crash.
//Magnus
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
TEXT_P(1)" appears to return a struct with vl_len set t
2139062143, which seems. Eh. Wrong? :) But this does not happen on the
*first* call to to_tsquery() which shows a proper text, but subsequent
calls show what lokos like garbage a couple of times, and then the
WARNING about the write pas
ting.
Not entirely sure how much that helps. Don't have time to dig in more
right htis minute, but I'd definitly appreciate some pointers into what
to look at next.
//Magnus
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Magnus H
tted another problem with taht code that
might require slightly more code than a one-liner to fix. We'll know in
a while when Teodor has analyzed it completely.
//Magnus
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Magnus Hagander
doesn't go away, look for something else installed that
might be interfernig with the normal operation of your windows install.
//Magnus
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Haile
> Sent: den 27 november 2006 15:21
sses.
Bye,
Gergely Czuczy
mailto: [EMAIL PROTECTED]
We've had some issues with the DNS configuration on the wwwmaster
server, that has caused all our email-accepting forms to malfunction.
Hopefully this should be fixed now for all cases.
//Magnus
---
is certainly slightly easier.
> Perhaps some usability testing prior to your next release would help.
Certainly. Do you have any resources from a usability testing lab to offer?
If not, I will attempt to adjust the few actual points that you do have
in this email, and leave the rest to all the people who claim our
install is a lot easier than most other databases.
//Magnus
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
NGW.html.
If you just want to get the binaries in there and just use the database,
get the MSI file from the main FTP site and install from there. See
http://pginstaller.projects.postgresql.org/.
//Magnus
---(end of broadcast)---
TIP 7: You can help
tion contains the
PostgreSQL documentation. In order to avoid installing two copies of the
documentation, the pgAdmin version will always be installed. This
version is also in a compiled CHM format which makes it easier to browse.
//Magnus
---(end of broadcast)-
, but we'll get there
eventually ;-) We are doing some of the work needed to get there, such
as updating the build system for Visual C++ 2005, on the way to 8.3, but
it's impossible to say when we'll have an actual 64-bit version.
//Magnus
---(end of b
*non*-admin account? Postgres is supposed to have a non-admin account to
run from.
//Magnus
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
found for that I guess.
//Magnus
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
To me this sounds like the theme is broken. Especially since we only use it to
look for terminal services stuff iirc. it'd be interesting to see if this can
be
reproduced on a different non standard
theme.
/Magnus
--- Original message ---
From: Ilya Kogan <[EMAIL PROTECTE
On Thu, Jan 25, 2007 at 07:37:21AM -0500, Ilya Kogan wrote:
> Magnus Hagander wrote:
> > To me this sounds like the theme is broken. Especially since we only use it
> > to look for terminal services stuff iirc. it'd be interesting to see if
> > this can be
> &g
g)
Did some googling, and it looks like at least Windows CE does not have
support for the kind of shared memory that we do. Don't know about XP
Embedded.
//Magnus
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ruser (and a diff pwd).
>
> Tried searching all forums but no result.
>
> I just hope someone sees this message and comes up with a solution rather
> than ask my cryptic questions in return
What are the permissions on the directory c:\program files, and what are
the permissions on
cmd.exe or Java. If it has been changed, documentation on how
> to access it would be useful for app developers.
This is not a bug, it's a feature ;-) It's written to the console, not
to the standard stream. If you launch the tools externally and want to
pass the password, you should
thout feedback,
we can't make it better, because it works fine in all "normal"
situations for thousands of other people. We want to know *why* it
didn't work in your case, so we can fix it or at least document it.
//Magnus
---(end of broadcast)--
ix, IIRC.
> Given the issues with PGPASSWORD and password.conf, would you folks
> consider putting the Password: prompt back the way it was?
I doubt it. I don't hold a strong opinion myself, but I think it has
been proposed and rejected before.
//Magnus
---
e= are valid while the manual (section VI) only mentions -U. Should
> the manual entry be edited?
Yes, I beleive so. Same problems are present for at least -W also, and
also present on pg_restore. so yes, that should be fixed. I'll try to
put together a patch unless beaten to it.
//Magnu
at table, SQLServer wil always do an indexscan -
because there is no way to heap-scan such a table. And second, since
SQLServer has covering indexes, they can use indexes in cases where it
returns even a significant portion of the table.
//Magnus
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
estart i stop and start the postgresql
> service again the problem doesn't appear anymore before next computer
> restart.
I think you need to give more information on how to reproduce this. Does
it happen right at restart, or later? What commands cause it to happen?
What configurat
Dj02 wrote:
> It's in default values and it gives the errors staight away. It will
> always fix when i restart PostgreSQL service.
>
> Magnus Hagander kirjoitti:
>> Mika Vimpari wrote:
>>
>>> The following bug has been logged online:
>>>
>>&g
his is a bug or there is something I'm doing wrong?
Can you check the permissions on your pgsql directory? If your account
only has permissions through the admin or power users group, you will
need to grant it explicit permissions (since it gives up admin and power
users when it starts)
//Mag
On Mon, Feb 12, 2007 at 09:08:11PM +0100, Filippo Toso wrote:
> Dear Magnus,
>
> > Can you check the permissions on your pgsql directory? If your account
> > only has permissions through the admin or power users group, you will
> > need to grant it explicit permissions
h full rights. Can you please
> help me to fix this?
did you check what's in the logfile?
Also, check the permissinoso n the install path and all the way down -
full permissions for *your* account is required to set the permissions
(the service account only needs read on things except the da
On Wed, Feb 14, 2007 at 01:49:43PM +0100, Filippo Toso wrote:
> Dear Magnus,
>
> > > The pgsql directory privileges are set to Everyone (Full Control).
> >
> > Hmm. Bummer. I really thought that was it. Can you check the full
> > directory tree up to the
nteresting thing would be to see the server logs, not the
application logs. Specifically, an issue that could look just like this
was fixed in 8.1.7, in which case you would see weird error messages
about permission denied or such in the *server* logs. None of that would
show up in t
nf file.
I think you are confusing server-side configuration with client-side
configuration. pg_hba is *only* parsed by the server, and the client has
no effect on it at all.
It looks a lot like you have a pgpass.conf file on your Windows machine,
possibly created by clicking "save passwor
ut never had the time to fix it)
Perhaps a reasonable thing to do would be to have the shortcut point to
a .BAT file that does a "pause" only if psql exits with a non-zero
exitcode.
Is this reasonable? Will psql always exit with non-zero when something
like this happen and also importantly, willi t always exit with a zero
exitcode if there is no problem?
//Magnus
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
you will.
>
> When you create a superuser with a semi-colon or quotes the error dialog
> starts "Passwords may not conain quotes..." missing the "t" in contain.
Thanks for reporting this, it has been fixed for 8.2 and all future
releases.
//Magnus
--
er
cases, as Bruce pointed out.
I guess another option would be to add a commandline option to psql to
pause on error, but I don't think that's going to fly ;-)
//Magnus
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
nd of make the base dn unnecessary ;-)
> (2) suffix containing ',' is converted to other character. This bug is
> caused by parsing algrithm to treat comma as a token separator.
For some reason, I can't get my AD to accept my LDAP connection on my
test machine - it
The following bug has been logged online:
Bug reference: 3147
Logged by: Magnus Hagander
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows
Description:Test bug report
Details:
This is just a test bug report to make sure that the bug
he fork() call. I'm not sure
if 12x slower is a representative figure, but it certainly could be.
You really should be using persistent connections, that will make the
problem almost go away.
//Magnus
---(end of broadcast)---
TIP 9: In versions
101 - 200 of 556 matches
Mail list logo
