You appear to have the situation in hand and the issue is quite easy to work
around now that it has been identified. I can just await the roll out of
the next Windows build while avoiding the errant behavior.
As such I will be unsubscribing from the list, but can be reached if any
further test
Not being quite sure how to get jpegs into my Comcast space, it's been a
while since I had to share a screen cap, I just sent seven to you and the
list as an attachment. The message bounced back from the list. are you,
Dinesh, in receipt?
Ø Hi John,
Ø Thank you so much for your co-ordination on fixing this issue.
Ø I believe, i have found the cause of this. This is due to "VALID UNTIL
'1969-12-31 00:00:00';" option. For confirming this, do you mind to do the
following steps once again and let me know the status.
Yup. That
OK. I have done a quick test in my local windows 7.
1. I have logged into PG 9.2 as a super user("postgres").
2. Created new login role by performing right click on "Login Role" - >
"Create New Login".
3. Entered the new login name and password.
4. Disconnected from pgAdmin and re-logged in the
Apologies that this got sent to Dinesh rather than the mailing list. L
Hi Dinesh,
Sorry, I reread my original request for help and it was extremely unclear as
I wrote it.
Basically, I was using the PGAdmin interface to set passwords, and the
interface reported that I had set them succ
I'm migrating some moderately sized DBs from Access to Postgres because I
can't deal with Access' performance issues and ANSI SQL noncompliance.
I hit a snag at a rather unexpected place. Before we get started I should
state that I'm using PGAdmin 1.16.1 on a Windows 8 64 bit machine. I'm
awa
