we got a new coredump of 7.3.7 today. this instance was running on a
freshly installed computer, to eliminate(?) all hardware issues. it's
still the same brand and model, though. the old system has been
running hard disk tests 30+ hours with no errors yet.
the core dump happens at the same
Kjetil Torgrim Homme [EMAIL PROTECTED] writes:
how can att[i]-attlen possibly change in the interim? but
data_length looks corrupted, too.
Unless you compiled with no optimization at all (-O0), the compiler
would likely fold the identical memcpy() calls in the different
if-branches together.
The following bug has been logged online:
Bug reference: 1249
Logged by: William Schaub
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.3
Operating system: Slackware 10 (Linux 2.4.27)
Description:pg_restore doesnt handle restoring databases not created
The following bug has been logged online:
Bug reference: 1250
Logged by: Aidan Dixon
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Sun/Solaris9/64bit
Description:compilation fails in src/backend/storage/lmgr/s_lock.c
Details:
PostgreSQL Bugs List [EMAIL PROTECTED] writes:
When restoring databases with pg_restore with the -C
option it will connect to template1, set authorization to
the user that created the database and then reconnect
as the user that created the database to the new database. this is where the
PostgreSQL Bugs List [EMAIL PROTECTED] writes:
The code in s_lock.c uses a .seg directive where .section seems to be
in vogue, judging from the output of cc -S for a simple hello world type
program.
Hmm. So how can we distinguish your version of Solaris from the ones
that want .seg?
Did I miss something that I should so to make 8.0beta2
for Mac OS X. I read the README and install and I see
no specific instructions for OS X.
Here is the info where the make fails.
OS X 10.3.5
gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build
1666)
What else can I send to you?
Ted
gcc
Theodore Petrosky [EMAIL PROTECTED] writes:
Did I miss something that I should so to make 8.0beta2
for Mac OS X.
Last time I tried it (which was a couple weeks back), our CVS tip built
perfectly cleanly on OS X. Other people report success too, modulo that
silly minus-zero bit in one
I downloaded the beta 2 source,
./configure --with-rendezvous
make
no other configurations... I did this same
configuration on the beta 1 and it was fine. (other
than a make check that we had to add an env line..)
I am going to try again by throwing away the folder
that starting fresh...
Ted
How's this one...
I realized that the machine I was testing on was
running '[EMAIL PROTECTED]'.. so I quit it.. Lo and behold
beta 2 compiled and made (with make check) just fine.
Thanks
Ted
--- Tom Lane [EMAIL PROTECTED] wrote:
Theodore Petrosky [EMAIL PROTECTED] writes:
Did I miss
Got something really odd happening here.
Simple test program, in java, with jdbc, postgres 7.4.5, on a redhat linux
system... app does a heavy loop of a prepared UPDATE, then Commit, 1s
of times. the table has a few columns, nothing fancy at all.On our
Redhat Enterprise 2.1 server
POSTGRESQL BUG REPORT TEMPLATE
Your name : Ralf Burger
Your email address : [EMAIL PROTECTED]
Here are the steps I am taking during the install of
postgresql-8.0-beta1-20040809.msi:
Screen 1 (warning):
next
Screen 2 (license)
next
Screen 3 (options)
leave default
next
Screen 4 (service config)
Service ID: pgsql-8.0-beta1
Service Name: PostgreSQL Database Server 8.0-beta1
Noted error appears on
windows XP, Serice Pack 1
with
postgresql 8.0 beta 1
using the installer.
After that, connection attempts via psql end with
psql: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing
System: Mac OS X 10.3.5
Pg: 8.0.0 b2
type_sanity ... ok
opr_sanity ... ok
test geometry ... FAILED
test horology ... ok
test insert ... ok
test create_function_1... ok
===
1 of 96 tests failed.
John R Pierce [EMAIL PROTECTED] writes:
Got something really odd happening here.
Simple test program, in java, with jdbc, postgres 7.4.5, on a redhat linux
system... app does a heavy loop of a prepared UPDATE, then Commit, 1s
of times. the table has a few columns, nothing fancy at
Ralf Burger [EMAIL PROTECTED] writes:
./postgresql-8.0.0beta2/bin/psql template1
./postgresql-8.0.0beta2/bin/psql: error while loading shared libraries:
./postgresql-8.0.0beta2/bin/psql: undefined symbol: PQserverVersion
You're linking against an old (pre-8.0) libpq. Check your ldconfig
John R Pierce [EMAIL PROTECTED] writes:
Got something really odd happening here.
Simple test program, in java, with jdbc, postgres 7.4.5, on a redhat
linux
system... app does a heavy loop of a prepared UPDATE, then Commit,
1s
of times. the table has a few columns, nothing fancy at all.
Hello,
Thank you for contacting eFax.com.
The e-mail address [EMAIL PROTECTED] is used solely for the sending
of signup confirmations to eFax Free subscribers. Messages sent to
[EMAIL PROTECTED] trigger this automated reply and are not read by
our Customer Service team.
If your message was
There is, however, an ownership problem with restoring sequences
in 8.0.0beta. In 7.4.5, for example, pg_dump issues a SET SESSION
AUTHORIZATION command and then creates a table, so implicitly-created
sequences are restored with the correct ownership. In 8.0.0beta2,
however, pg_dump doesn't
However, of course the best thing is to just fix it, which I guess I'll
have a crack at...
Given that pg_dump does put out GRANT/REVOKE operations on the sequence,
it's certainly aware that the sequence exists. I suspect this is just a
fixable bug (ie, suppression of output of the sequence
Fabien COELHO schrieb:
328 [main] DEBUG com.mosaicag.rwa.dbutil.standard.DefaultCsvExport -
executing SQL-Stmt: SELECT * FROM transaction WHERE transaction_date =
to_timestamp('01.01.2002', 'DD.MM.') AND transaction_date
to_timestamp('01.01.2003', 'DD.MM.')
java.lang.OutOfMemoryError
[ fix broken CHECK_FOR_INTERRUPTS macro ]
Applied. I see how this might change detection of
statement_timeout, but I do not actually see what it's got to
do with deadlock detection.
In the deadlock situation the process that needs to wake up
is going to be blocked on a semaphore, and
Hi there!
I just installed PostgresSQL 8 beta1 for Windows ( I have WinXP ).
I launched pgAdmin III and created one test DB. So, it was created.
Then, I launch my Zend Studio and tryed to connect to this new test DB
using next code to check connection:
?php
$psConn = pg_connect( dbname=jimmyDB
[Tom Lane]:
This evidently corresponds to data starting at offset 0ffc on the
disk page (the last few bytes of the gdb output match the start of
tuple 43, which is in the next higher part of the page --- note
that the bytes are being printed in opposite orders by pg_filedump
and
Hello,
I've been testing PostgreSQL v8.0 on my Win2000 machine and it seems
pretty stout. However, I have come across some issues that concern me:
1. All earlier versions of PostgreSQL are able to be editted via an ssh
Shell or some other Unix-based platform. But when I try to edit any of
This is the last log file
Postgresbug.rar
Description: Binary data
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Thought you might like to know:
Red Hat Advanced Server 2.1 (based on Red Hat 7.2) on an HP DL380 dual Xeon
x86 server
Linux 2.4.9-e.41enterprise #1 SMP Wed Jun 16 23:33:07 EDT 2004 i686 unknown
gcc version 2.96 2731 (Red Hat Linux 7.2 2.96-128.7.2)
glibc-2.2.4-32.15
./configure
make
make
Hi,
Weve been using Postgres for about a year. I
recently installed the beta 8.0 Windows version on my XP laptop. It
worked fine for about a week, but now the service will not start.
Heres the message I receive:
Any ideas?
Michael Hornick
Insurance
Systems Inc.
On Fri, 10 Sep 2004, Tom Lane wrote:
PostgreSQL Bugs List [EMAIL PROTECTED] writes:
The code in s_lock.c uses a .seg directive where .section seems to be
in vogue, judging from the output of cc -S for a simple hello world type
program.
Hmm. So how can we distinguish your version of Solaris
Was the install very good, however am I needing to
do something similar in the subject of the install to create users and services
in Windows 2000/xp for an application, will it be that you could order me the
script or project that you set up for this version 8.0
beta? Question: Does the
Hi,
I have a set of libraries and C/C++ programs with embedded access to
a PG database. I'm using ecpg. I'm working on a Linux RedHat9 platform.
Until now I was in PG 7.4.2 :
[EMAIL PROTECTED] SrcLib]$ ecpg --version
ecpg (PostgreSQL 7.4.2) 3.1.1
[EMAIL PROTECTED] SrcLib]$ g++ --version
g++ (GCC)
Dear friends
I'm not able to install postgresql on my Windows Machine:
RDBMS Version: 8.0.0 beta2-2dev
OS: Windows 2k - all patches installed (up to date)
After klicking o.k. in the window that displays the Release Notes,
installation abords with the following message:
Installation ended
--- Tom Lane [EMAIL PROTECTED] wrote:
Did you invoke any of the build steps with a
relative path (eg,
../configure)?
Yep.
There are some known problems in
beta1 with
reducing relative paths to absolute. I think this
probably
explains your issue, though I did not see that
specific
What if they change the owner of the serial sequence independently
anyway?
I suppose a complete solution would involve forbidding that. We don't
allow you to alter the owner of an index independently of its parent
table ...
Problem is existing dump files. Oh, hang on - this is new for 8.0.
Hmm ... I hadn't thought of that approach, but it seems pretty
reasonable offhand ... comments?
What if they change the owner of the serial sequence independently
anyway? Then dumps will be restored incorrectlynot that it matters
perhaps...
Chris
---(end of
I just installed Postgres 8.0.0 in my PC environment. I
created the necessary users and rebooted the system. Saw that the post_svc.exe
and the postmaster.exe are running. However, the minute I try to connect to template
I get too many clients already. Check your license Whats
this all
Title: bug
Hi could you help me resolve the following when trying to start the DB.
$ ./postmaster -D /data1/pgdata
IpcMemoryCreate: shmget(key=5432001, size=1417216, 03600) failed: Invalid argume
nt
This error usually means that PostgreSQL's request for a shared memory
segment exceeded
POSTGRESQL BUG REPORT TEMPLATE
Your name : Stephan Sachse
Your email address : sachse
39 matches
Mail list logo
