they
have a MMU, so they can't run a 'regular' linux kernel.
frankly, these don't seem like good candidates for a relational database
server to me.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list
disappear. Two concurrent connections (one from
a console and another from the app) could be contradicting themselves, one
giving the error and the other not.
that sounds like a hardware/platform problem to me more than anything.
maybe in memory cache is getting corrupted or something?
--
john r
on win7?
p.s please direct replies to pgsql-bugs@postgresql.org and not me
personally.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription
. for instance, at a CMD ('dos') prompt, type the
command,
ECHO %COMSPEC%
and you should get something like...
C:\WINDOWS\system32\cmd.exe
p.s please direct replies to pgsql-bugs@postgresql.org and not me
personally.
--
john r pierce 37N 122W
/current/static/bug-reporting.html
oh, direct further correspondence to the bug list,
pgsql-bugs@postgresql.org and not me personally
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs
towards product
maintenance and updating.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
pg_upgrade to move from 9.1.6 to pg 9.3?
having multiple tablespaces on different mount points complicates
things. I'm not sure how or if pg_upgrade handles that.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
prompt has no idea what means.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
it.
CREATE USER User WITH PASSWORD 'somekindapassword';
Note the same is true for tablespaces, if you use those.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
On 8/30/2013 11:33 AM, Kevin Grittner wrote:
but
you might just be dealing with dead space from deletes and updates.
I would suggest 'likely are' rather than 'might be'.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via
On 8/10/2013 4:57 PM, karsten.l...@gmx.ch wrote:
The following bug has been logged on the website:
Bug reference: 8380
Logged by: Karsten Lenz
Email address: karsten.l...@gmx.ch
PostgreSQL version: 9.2.4
Operating system: CentOS 6.4
Description:
Hello,
initdb is ignoring
search_path, which is $USER, public... name the
schemas same as the users...
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
On 5/31/2013 4:29 PM, Gerald Luger wrote:
Shouldn't I expect all results to be 000...0001?
Otherwise it would be
1 != 1?
SQL's BIT type is big endian, a hangover from its IBM mainframe heritage.
--
john r pierce 37N 122W
somewhere on the middle
numbers bits such that bit 0 is the most significant bit of a word.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
entry for the postgres server, so if you change it in
Local Users when you have an existing postgresql server install, then
you have to find the postgresql service in the Services manager, and
change the password the service uses to start there.
--
john r pierce
software.
btw, this is NOT a 'bug report' and does NOT belong on the pgsql-bugs
mail list, you should subscribe to the pgsql-general list for further
discussions.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
:00:00 postgres: autovacuum
launcher process
postgres 38433 38425 0 01:59 ?00:00:09 postgres: stats
collector process
postgres 39450 38425 85 05:38 ?01:49:02 postgres: postgres
pgbench [local] ALTER TABLE
--
john r pierce 37N 122W
somewhere
On 5/12/2013 9:10 AM, Chaya Gilburt wrote:
PostgresSQL Version 8.7.1
hopefully, you mean 8.1.7 ? there never was a 8.7 release, it went up
to 8.4 then rolled over to 9.0
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent
this, and see WHY
the server terminated
but I concurr with Heikki, upgrade to 8.4.latest (currently 8.4.17) and
if this still occurs then figure out why.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
On 4/30/2013 2:55 AM, Bansal, Pradeep wrote:
Also with the debug5 mode the logs are:-
well, I don't see any backend crashes there.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
).
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
connect as anyone other
than themselves
authentication types are managed via pg_hba.conf
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
your example, as your example has to scan every
single row of the whole mess. not sure where Filter: (cid=1) comes
from, since you showed the query as SELECT COUNT(*) FROM dna_strands;
--
john r pierce 37N 122W
somewhere on the middle of the left coast
268 child partitions. that is, in my experience,
way too many. we try and keep partitions under a few dozen even on our
multi-terabyte tables. 6 months by week is about as far as we go.
with your 10 year data, I'd probably partition by quarter, or something.
--
john r pierce
much simpler than changing the
search_path, which is persistent to the connection and likely will
backfire if your apps are changing it to something else.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
a password there.then
tell the postgres installer what you set it to.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
on the pgsql-general email list, not as a
'bug report'.
and, there's not enough info here to even begin to guess whats wrong.
maybe you should take this up with your hosting company, if you're
running their OS configuration.
--
john r pierce 37N 122W
, and set a
new password via right click... then install the newer postgres and
tell it what that password is.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
of it. This
package supports PostgreSQL ? what version(s) do they recommend? does
it require additional database connectivity components like ODBC, or
NPGSQL or ?
anyways, I don't believe this is a postgresql bug, so doesn't belong on
this list.
--
john r pierce
on the number
of database objects than their size.)
do note this -k option only functions if the old and new cluster are on
the same mount point, so the files can be mv'd
--
john r pierce 37N 122W
somewhere on the middle of the left coast
On 2/15/2013 4:27 PM, Bruce Momjian wrote:
do note this -k option only functions if the old and new cluster are on the
same mount point, so the files can be mv'd
Actually, hard linked, not moved.
errr, that. right. ;)
--
john r pierce 37N 122W
thing), or just use text (no length specified), these
formats return just what you store ('joe blow' will return an 8 char
string).
--
john r pierce 37N 122W
somewhere on the middle of the left coast
On 1/14/2013 3:04 AM, fahar.ab...@enterprisedb.com wrote:
PostgreSQL version: 9.2.2
Operating system: Windows 7, Windows 2003 Server
Description:
I am facing an issue while installed downloaded postgis build.
Version:
PostgreSQL-9.2.2
Steps:
1. Install PostgreSQL 9.2 windows 64 on Windows 7
On 12/24/2012 2:17 AM, Michael Felt wrote:
*postgresql-8.3.22.tar.bz2* (in progress)
Unpacking the archive has an error. There are couple references to a
file @LongLink (contents)
$ cat @Long*
postgresql-8.3.22/src/backend/utils/mb/conversion_procs/utf8_and_euc_jis_2004/utf8_and_euc_jis_2004.c
On 12/5/2012 4:40 AM, Branka Stancic wrote:
I have problem.
I want to restore only data in database.
In pgAdmin I was backup only data from old database and now i have
backup file backup.sql.
In terminale I want restore only data in new database and I using
command pg_restore -i -h localhost
On 12/4/2012 1:38 AM, Duggirala, Manikanth (TCS) wrote:
Can you please let us know if PostgreSQL v8.1.11 is compatible with OS
2008 R2 ?
8.1.anything shouldn't be installed today, its an obsolete deprecated
version.
that said, IIRC, there were major issues with versions prior to 8.3 on
in your /etc/hosts file?
I've seen systems where localhost is 127.0.0.1 and localhost6 is ::1...
RHEL systems come that way.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
--
john r pierceN 37, W 122
santa
is
setting localhost to both 127.0.0.1 and my other IP. Using
`listen_addresses = '127.0.0.1'` fixes the problem.
fix your /etc/hosts thats an artifact of the #@$@# RHEL installer,
if the network isn't properly configured at install time, it loves to do
that with the hostname.
--
john r pierce
On 10/23/12 4:26 AM, Sree Krishna Priya Kuppa wrote:
Hi Team,
Required a copy of PostgreSQL to install on z/linux i.e Suse Linux
64-bit on OS/390. Please suggest where to get the setup file.
if suse doesn't provide that, you'll likely need to compile your own.
--
john r pierce
elevation prompt before you can write to Program Files,
install services, and other such similar activities.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
it this way, you're not editing any files that are under RPM
package management, so you're not going to get bit during updates.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs
);
since no id is likely to be null or an empty string, the odds are, it
will be returning 999 if there are any records and 0 if there aren't any.
what exactly do you WANT to do?
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
On 09/13/12 12:17 PM, te wrote:
FOR r in select distinct(id) from temp
select clean()
what is this selecting records from? what is temp ?
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql
remember what it was
called.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
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/09/12 9:31 PM, John R Pierce wrote:
2/ Is anyone working on parallel query execution?
someone presented a FOSS project on the pg-general list the other day
that implements parallel execution using a postgres based engine, but
it only supports fairly simple queries. I can't say I
degradations with larger shared buffers.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
On 08/15/12 9:02 AM, Valentine Gogichashvili wrote:
On Wed, Aug 15, 2012 at 3:40 PM, John R Pierce pie...@hogranch.com
mailto:pie...@hogranch.com wrote:
On 08/15/12 6:36 AM, Bruce Momjian wrote:
We warn against making shared buffers 8GB, and this is
perhaps another
of potential interest in this bug report would be any
unusual or exceptionally large settings in postgresql.conf, is this a 32
bit or 64 bit install
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list
postgres.
LOCAL_SYSTEM created the files, and owns them.
Oh, the pss-svc user should not be a member of Administrators.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
the user in services.
the SERVICE account ('postgres') needs only 'run as service' privileges.
the user doing the start/stop needs admin privs.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing
on pg-general.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
on lgen_fraud_email o (cost=0.00..393.72
rows=20072 width=32)
without seeing the query, I can only suggest that it appears the LIMIT
is inside of a nested query or something, as it looks like it was
applied prior to additional filtering and joining.
--
john r pierce
building on AIX 6.1 using IBM
XLC. I'm not connected to the build machine at the moment, so I'd have
to dig to find my build instructions (and, of course, XLC is a $$$
compiler).
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
, and then SELECT 1's, no
other query is executed.
Lose the BEGIN and it will probably work more nicely.
indeed,a 1-5 hour long transaction means VACUUM can't clean up anything
newer than the oldest active transaction, and thats not per database,
thats cluster-wide.
--
john r pierce
that it is also doing the same thing for custom and tar
backups as well.
windows filesystem APIs are perfectly happy with forward slashes in
paths, always have been.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via
(below)?none of this appears
to have anything to do with PostgreSQL
I see references to EnterpriseDB (com.edb, as well as the username), so
perhaps you should contact them, as they support their own software.
--
john r pierceN 37, W 122
santa cruz ca
file store, in particular,
there's no guarantee that writes will be done in a valid order or even
that random writes will work correctly. the fact that it seemed to
work in a much older version was purely happenstance.
--
john r pierceN 37, W 122
santa cruz ca
is the error you're getting?
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
-general email list.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
'
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE NOREPLICATION;
It would be a bug in jdbc? I am using PostgreSQL 9.1 and linux.
what is the problem?
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql
r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 11/10/11 1:15 PM, Alexey Nalbat wrote:
= select '10 weeks'::interval;
interval
--
-1589934592 days
a billion weeks is like 19 million years. somehow, I don't think that
postgresql's date math has quite that range.
--
john r pierce
away. Sigh. this all conspires to make it really hard to
help someone out remotely.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
this is the wrong list for
this discussion.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
is assuming postgres is running on the same server
which of these two statements makes more sense?
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
on the slave side
would render the WAL files inherently unusable.
to do what you want would require using a fundamentally different
replication method, such as Slony or Bucardo.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent
On 10/17/11 7:41 AM, Andreas Pflug wrote:
Sounds much too straight forward, not mysql-ish autistic enough...
I fixed your spelling. HTH!
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql
On 10/12/11 9:28 AM, Kevin Grittner wrote:
This is not a bug. The workaround is to not drop the database which
is automatically created on installation.
or to explicitly connect to another database to do the create
--
john r pierceN 37, W 122
santa cruz ca
important is what perl is in the POSTGRES SERVICE's path, not your
desktop users. windows doesn't make this easy to determine.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs
r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
, alternately, it could be 'trust', but this would say
any process or user on your system could connect as any postgres role
without any verification or authentication at all. caveat emptor.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
On 08/30/11 10:25 PM, Lampa wrote:
Also tried change maintenance_work_mem to 2G and same result.
Imposible to set over 2GB (FATAL: 3145728 is outside the valid range
for parameter maintenance_work_mem (1024 .. 2097151))
is this a 32bit postgres ?
--
john r pierce
the clients do not inherently support by checking the configuration
of the server.
libpq running in the client user's context usually has no access to the
postgresql.conf file which is generally in a mode 700 directory owned by
the service account.
--
john r pierceN
/Guide_to_reporting_problems
D) this wasn't a 'bug' by any stretch of the imagination.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
should be able to START the service.
note this password you set in User Manager has nothing to do with the
password (if any) for the postgres role you use to log onto the database
server for administration.
--
john r pierceN 37, W 122
santa cruz ca
platforms such as
Solaris. I have zero OS X specific knowlege
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
On 05/10/11 8:09 PM, 李紅兵 wrote:
I run my test program with 2 ways in the same login environment.One
succeed and one fail.
1) psql -d dbi_link_test
--connect succeed
2) psql -h HOSTNAME -d dbi_link_test
--connect fail
The different is connection options(Unix Domain Sockets/TCP Sockets).
is
On 04/28/11 12:33 PM, Brian S. Krug wrote:
The following bug has been logged online:
Bug reference: 5996
Logged by: Brian S. Krug
Email address: bk...@usatech.com
PostgreSQL version: 9.0.3
Operating system: Solaris
Description:CURRENT_TIMESTAMP uses often undesired
On 04/15/11 12:33 PM, Yanish wrote:
The following bug has been logged online:
Bug reference: 5983
Logged by: Yanish
Email address: yanish_3...@hotmail.com
PostgreSQL version: 9.0
Operating system: Windows Seven 64-bit
Description:creating accounts
Details:
hello i
On 04/15/11 2:04 PM, Rikard Pavelic wrote:
This feature would reduce object-relational impedance mismatch in DDD,
objects aren't relational.deal with it. OOPS may be a reasonable
methodology for coding, however its purely hierarchical, and doesn't map
at all well to relational calculus.
On 04/07/11 6:53 AM, Halli, Savita wrote:
Yes, I am going through that. Its mentioned that some of the commands need to
be run. My question is how frequently we need to run those commands(commands
for db maintainance).
how frequently do you need to do file system maintenance? or for that
On 03/31/11 6:50 PM, Raphael Giovanini wrote:
I`m change the default passwod, and not conect for this user. What the
default password?
there is no default password. on most unix and linux distributions, the
default authentication mode is set to 'ident' which means a given unix
user X can
On 03/23/11 4:32 PM, Nathan Davalos wrote:
...
SET CLIENT_ENCODING TO 'WIN1251';
copy tmpintermediate from 'thefile.txt';
Sample contents of thefile:
230002 Alto Desempeño, S.A. De C.V.
When using WIN1251 or WIN1252 I get nothing in the second field, it just
ignores the data. Same thing for
On 03/23/11 5:42 PM, Nathan M. Davalos wrote:
Just in case the reply didn't go through the character in question is F1.
I replied to the message using pgsql-bugs@postgresql.org, but I'm a wee bit
new to the bug reporting stuff using the mailing list.
The hex of the file in total is
On 03/22/11 1:40 PM, Josh Berkus wrote:
All,
At two sites I'm not allowed to share data from (grrr), I've encountered
core dumps of psql. In once case the core dump happens as soon as you
run any query. In the second case, it occurs when you exit.
What both sites have in common is that
On 03/11/11 12:18 AM, Ferenc Lutischan wrote:
The following bug has been logged online:
Bug reference: 5924
Logged by: Ferenc Lutischan
Email address: yours...@freemail.hu
PostgreSQL version: 8.3.14 - 9.0.3
Operating system: Linux
Description:bug or feature?
On 03/03/11 6:56 PM, Cristian Lazarte wrote:
The following bug has been logged online:
Bug reference: 5913
Logged by: Cristian Lazarte
Email address: cristianlaza...@hotmail.com
PostgreSQL version: 8.0.2
Operating system: WINDOWS XP
Description:invalid page header
On 02/27/11 7:13 PM, Gie Rizkiadi wrote:
I have installed PostgreSQL 8.4.1 running on 112 Embedded PC OS Microsoft
Windows XP Embedded Version 2002 Service Pack 2 Intel(R) Atom(TM) CPU N270
@1.60 GHz 1.32 GHz, 0.99 GB of RAM and 8GB Harddisk ( 6GB Free ) which are
connected to LAN, most of that
On 02/08/11 10:20 AM, Tom Lane wrote:
Cyril DE MURCIAcyril.de-mur...@dcnsgroup.com writes:
We use postgresql 7.3.2 under Linux Red Hat 9.0.
We periodically dump and restore our database. I don't know if an error
occured during a dump restore but our DB seems to be corrupted.
Our base contains
On 01/14/11 8:12 PM, Aren Cambre wrote:
This came from pgAdmin's *Default value* field. This field is supposed
to accept anything other than a string?
default value can be any valid expression
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
On 12/28/10 3:22 PM, Peter Eisentraut wrote:
On tis, 2010-12-28 at 12:19 +, Mario Ohnewald wrote:
However, during the make, postgres requires perl devel. Should this
not be covered in the configure script?
No, it's not configure's job to do the job of make or the compiler.
I believe he's
On 12/27/10 10:31 PM, Trimurthulu Bandaru wrote:
Can you produce a single .sql file that creates the tables and does the
problem insert?
Can you please make me clear in this issue..
he's asking if you can produce a test case in the form of a .SQL file
that creates a schema and demonstrates
On 12/23/10 2:34 AM, Marc Cousin wrote:
No, from a Linux psql client (inside a kde konsole). You can setup any charset
in it. I have exactly the same behaviour with psql under windows anyway, with
a chcp 1252 in the cmd console. It's not a console charset problem, I've
tripled checked that :)
On 10/25/10 7:50 AM, Marcus wrote:
The following bug has been logged online:
Bug reference: 5723
Logged by: Marcus
Email address: marcusboos...@mailinator.com
PostgreSQL version: 9.0.1
Operating system: Ubuntu 10.10
Description:Can not start postgres after install
On 10/11/10 4:09 PM, Chris English wrote:
C:\WINDOWS\system32pg_dumpall.exe --port 5433 username--postgres
--schema-onl
y c:/windows/system32/pg_upgrade_dump_all.sql
Access is denied.
why are you writing the .sql output to the windows system32 directory?!?!?
thats a TERRIBLE place to put
On 06/30/10 3:23 PM, Bidski wrote:
Hi all,
I downloaded the one-click installer for PostgreSQL 9.0 beta2 for
Windows x64 (postgresql-9.0.0-beta2-windows-x64.exe) and installed it
on my Windows 7 64 bit system. Installation seemed to go off without a
hitch, but when I tried to link to libpq in
On 06/30/10 3:40 PM, Bidski wrote:
John R Pierce pie...@hogranch.com writes:
wild guess says your project is 64 bit, but libpq.dll is 32 bit.
Why would there be a 32bit dll in the 64bit pre-built package?
look and see if there's another /lib64/ or similar directory ?
I didn't notice
On 06/23/10 6:02 PM, Chris Browne wrote:
There is already an FAQ on issues relating to AIX. It is, in recent
versions, part of the documentation tree:
http://www.postgresql.org/docs/9.0/static/installation-platform-notes.html
can I take this opportunity to point out a problem on that
Sunny wrote:
The following bug has been logged online:
Bug reference: 5496
Logged by: Sunny
Email address: goodmeet7...@naver.com
PostgreSQL version: 8.4
Operating system: windows xp
Description:Link does not open though wish to use following site
Details:
Link
1 - 100 of 191 matches
Mail list logo
