Re: [BUGS] BUG #4966: wrong password.....
Hi, "walkerlacombe" writes: > Operating system: vista home premium > Description:wrong password. > Details: > > when i boot up my pc i have owner and postgresql as users.for postgresql i > need a password. now when i downloaded postgresql i had to make 2 passwords. > now , when i try to get into the postgresql user it tells me that the > password is the wrong one.i have both of them and they don't work. in other > words i have no access it what so ever. so how do i retrieve thw password > that does work? Would we consider providing a documentation section explaining how to change pg_hba.conf to trust, reload, change password, get back to saner HBA if needed? This question is a such a FAQ that it deserves a place in the docs, I think. Is there a counter-argument (security based or anything) to add this, maybe in the tutorial part, a new Authenticating section between Architectural Fundamentals and Creating a Database? -- dim -- 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 #4966: wrong password.....
On Thu, 2009-08-06 at 11:22 +0200, Dimitri Fontaine wrote: > Would we consider providing a documentation section explaining how to > change pg_hba.conf to trust, reload, change password, get back to saner > HBA if needed? > > This question is a such a FAQ that it deserves a place in the docs, I > think. Sounds like a _REALLY_ good idea to me. I almost wonder if Pg on Windows needs a "safe mode" where it's launched with an alternate pg_hba.conf that trusts postmaster on 127.0.0.1, rejects *all* other logins, and doesn't listen on any external interfaces. People seem to lose passwords a _lot_ . Some info in the docs on changing/deleting the Pg service account might also not be a bad idea. -- 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
[BUGS] BUG #4967: polygon @> point incorrect for points close to shared borders
The following bug has been logged online: Bug reference: 4967 Logged by: Paul Matthews Email address: p...@netspace.net.au PostgreSQL version: 8.3.7 Operating system: Linux Open Suse 11.0 + 11.1 Description:polygon @> point incorrect for points close to shared borders Details: Have two polygons, both with many vertex, sharing a common edge. Several thousand points where then tested to see which of the polygons the points fell into using the "polygon @> point" operator. A number of points close to the common border claimed they fell into both of the polygons. A quick perl+DBI+GD application was developed to plot both the polygons, the polygon boundaries, as well as the points that thought they where in both. This showed points close, but still several pixels away from the shared border, thinking they where in both. Guidance on this matter would be appreciated. -- 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 #4966: wrong password.....
Craig Ringer writes: > On Thu, 2009-08-06 at 11:22 +0200, Dimitri Fontaine wrote: >> Would we consider providing a documentation section explaining how to >> change pg_hba.conf to trust, reload, change password, get back to saner >> HBA if needed? >> >> This question is a such a FAQ that it deserves a place in the docs, I >> think. > Sounds like a _REALLY_ good idea to me. I'd bet this has nothing to do with the OP's problem, though. > Some info in the docs on changing/deleting the Pg service account might > also not be a bad idea. That might... regards, tom lane -- 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 #4966: wrong password.....
Dimitri Fontaine wrote: > This question is a such a FAQ that it deserves a place in the docs, I > think. Is there a counter-argument (security based or anything) to add > this, maybe in the tutorial part, a new Authenticating section between > Architectural Fundamentals and Creating a Database? Well, if it's a FAQ, why not add it to the, err, FAQ? I just did: http://wiki.postgresql.org/wiki/FAQ#I_lost_the_database_password.__What_can_I_do_to_recover_it.3F Please expand on the answer; it is currently very brief. This FAQ could really use some love. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- 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 #4967: polygon @> point incorrect for points close to shared borders
"Paul Matthews" writes: > A number of points close to the common border claimed they fell into both of > the polygons. How close is "close"? There's some pretty arbitrary fuzzy-comparisons logic in the geometric datatypes ... see FPeq() and friends. That might be doing it to you. regards, tom lane -- 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 #4966: wrong password.....
"walkerlacombe" wrote: > PostgreSQL version: 8.0 > Operating system: vista home premium While Alvaro has very kindly added something to the "Frequently Asked Questions" (FAQ) page which might help you: http://wiki.postgresql.org/wiki/FAQ#I_lost_the_database_password.__What_can_I_do_to_recover_it.3F you should be aware that the above is not a supported environment. Note that on the Windows download page: http://www.postgresql.org/download/windows It says, "Only PostgreSQL 8.2 and above are supported on Windows." It might be best to go to 8.3 or 8.4, though. Each new major version contains significant improvements. -Kevin -- 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 #4958: Stats collector hung on WaitForMultipleObjectsEx while attempting to recv a datagram
> Yeah it will be interesting to see if the collector starts > functioning fine after the restart. That might hint that the > kernel object representing the socket is maybe fine but would > not prove conclusively that the issue is with PG code because > the layer used by WaitForMultipleObjectsEx might have issues too. This morning I planned to verify that stats collection was still not working before killing the stats collector and allowing it to restart. I had a psql session open from the previous day, but I closed it and tried to start a new session. I log each session and wanted to start a new log. Now, I am unable to start a new psql session. I get this error on the client side: | psql: could not send startup packet: Connection reset by peer (0x2746/10054) | and this error on the server side: | 2009-08-06 10:48:59.542 EDT,LOG: could not receive data from client: No connection could be made because the target machine actively refused it. | 2009-08-06 10:48:59.542 EDT,LOG: incomplete startup packet I didn't find too much in the archives about this. It's what happens if you just connect to 5432 (with telnet for example) and then drop the connection. Occasionally (3-6% of the time), I get this on the client side: | C:\postgres\bin>psql | psql: server closed the connection unexpectedly | This probably means the server terminated abnormally | before or while processing the request. and this on the server side: | 2009-08-06 11:16:27.933 EDT,LOG: could not receive data from client: No connection could be made because the target machine actively refused it. When this sequence happens, I can see a backend postgres.exe process start up and then exit very quickly. Note the absence of the "incomplete startup package" message. Could it be related to the stats collector problem? The stats collector on this system has been hung for over 6 weeks, so the timing of this problem is quite delayed. I have windbg on this system along with the source and the symbols, so I could look for anything in the debugger. -Luke -- 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 #4958: Stats collector hung on WaitForMultipleObjectsEx while attempting to recv a datagram
Luke Koops wrote: > When this sequence happens, I can see a backend postgres.exe process > start up and then exit very quickly. Note the absence of the > "incomplete startup package" message. > > Could it be related to the stats collector problem? The stats > collector on this system has been hung for over 6 weeks, so the timing > of this problem is quite delayed. Maybe you should try a network sniffer and see if you can spot anything weird. I think Wireshark can decode the Postgres protocol. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #4968: Uma ajuda
The following bug has been logged online: Bug reference: 4968 Logged by: Dielton Paulo Email address: dpa...@sefaz.ba.gov.br PostgreSQL version: postgre 8.4 Operating system: Windows XP Description:Uma ajuda Details: Boa Tarde, Trabalho na Secretára da Fazenda do Estado da Bahia, e nós estamos usando o postgre 8.4 estamos tentando acessar o postgre através do access 2000, mas ocorre um erro do tipo "Erro out memory in query". Se vocês puderem nos ajudar agradeço. Atenciosamente, Dielton Paulo -- 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 #4968: Uma ajuda
Pode falar ingles? This is an english mailinglist, otherwise you should try the portuguese mailinglist. What kind of query are you trying to execute? And what about the settings in postgresql.conf? Abraço, Frank Op 6 aug 2009, om 20:30 heeft Dielton Paulo het volgende geschreven: The following bug has been logged online: Bug reference: 4968 Logged by: Dielton Paulo Email address: dpa...@sefaz.ba.gov.br PostgreSQL version: postgre 8.4 Operating system: Windows XP Description:Uma ajuda Details: Boa Tarde, Trabalho na Secretára da Fazenda do Estado da Bahia, e nós estamos usando o postgre 8.4 estamos tentando acessar o postgre através do access 2000, mas ocorre um erro do tipo "Erro out memory in query". Se vocês puderem nos ajudar agradeço. Atenciosamente, Dielton Paulo -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs Frank Heikens frankheik...@mac.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 #4946: bug - libiconv-2.dll
On Mon, Jul 27, 2009 at 8:06 PM, Fabiano wrote: > > The following bug has been logged online: > > Bug reference: 4946 > Logged by: Fabiano > Email address: fabiano.san...@onda.com.br > PostgreSQL version: 8.3 > Operating system: windows > Description: bug - libiconv-2.dll > Details: > > error libiconv-2.dll That's not very specific. ...Robert -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #4969: ajuda
The following bug has been logged online: Bug reference: 4969 Logged by: Dielton Paulo Email address: dpa...@sefaz.ba.gov.br PostgreSQL version: 8.4 Operating system: Windows XP Description:ajuda Details: Good afternoon, Working in the Secretary of Finance of the State of Bahia, and We are using postgres 8.4 we are trying to access the postgres Access by 2000, but an error of type "error out in memory Query. " If you can help us appreciate that. Sincerely, Dielton Paulo -- 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 #4967: polygon @> point incorrect for points close to shared borders
Tom Lane wrote:
"Paul Matthews" writes:
A number of points close to the common border claimed they fell into both of
the polygons.
How close is "close"? There's some pretty arbitrary fuzzy-comparisons
logic in the geometric datatypes ... see FPeq() and friends. That might
be doing it to you.
regards, tom lane
I'll try to figure out how "relatively" close tonight, this stuff is
sub-metre resolution GPS data. The attached picture shows the two
polygons, the shared border, a road in this case, and the houses that
think they are on both sides of the road. Houses and other features are
located with latitude+longitude.
Last night I plugged in the polygon contains point code from
http://www.ecse.rpi.edu/Homepages/wrf/Research/Short_Notes/pnpoly.html.
This resolved to houses correctly. If it helps in anyway please see the
attached. No use of fuzziness. Opaque yes, fuzzy no. :-) . Use in any way you
see fit.
#include "postgres.h"
#include "utils/geo_decls.h"
#include "fmgr.h"
#ifdef PG_MODULE_MAGIC
PG_MODULE_MAGIC;
#endif
PG_FUNCTION_INFO_V1(kontains);
Datum
kontains(PG_FUNCTION_ARGS)
{
POLYGON* polygon;
Point* point;
int isin;
polygon = PG_GETARG_POLYGON_P(0);
point = PG_GETARG_POINT_P(1);
isin = contains( polygon->npts, polygon->p, point );
PG_RETURN_BOOL(isin);
}
int contains( int nvert, Point* vertex, Point* test )
{
int i, j, c = 0;
for( i=0, j=nvert-1; i
if( ((vertex[i].y>test->y) != (vertex[j].y>test->y))
&&
(test->x < (vertex[j].x-vertex[i].x) *
(test->y-vertex[i].y) /
(vertex[j].y-vertex[i].y) + vertex[i].x) )
c = !c;
}
return c;
}
<>
--
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 #4967: polygon @> point incorrect for points close to shared borders
Paul Matthews writes: >> How close is "close"? There's some pretty arbitrary fuzzy-comparisons >> logic in the geometric datatypes ... see FPeq() and friends. That might >> be doing it to you. > I'll try to figure out how "relatively" close tonight, this stuff is > sub-metre resolution GPS data. The attached picture shows the two > polygons, the shared border, a road in this case, and the houses that > think they are on both sides of the road. Houses and other features are > located with latitude+longitude. Hmm ... just out of curiosity, why aren't you using PostGIS for this? Our built-in geometric types are mostly an academic proof-of-concept, they aren't industrial strength IMHO. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #4970: Broken link in manual
The following bug has been logged online: Bug reference: 4970 Logged by: Rob Wultsh Email address: wult...@gmail.com PostgreSQL version: 8.4 Operating system: N/A Description:Broken link in manual Details: http://www.postgresql.org/docs/8.4/static/geqo-biblio.html links to "The Hitch-Hiker's Guide to Evolutionary Computation" (http://www.cs.bham.ac.uk/Mirrors/ftp.de.uu.net/EC/clife/www/location.htm) which as of 8/4/2009 responds with at 404 page. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
