After upgrading to v 7.3.4 I noticed this error message in the database
setup log:
grep: can't open data_path/conversion_create.sql
Turned out initdb is looking for conversion_create.sql.
We're not building this script and I may need to look into the build
process,
but for now can someone tell
I need to provide recommendations for optimal value for the
shared_buffers. This has to do with some optional feature
we have in our application. If turned on - a number of extra
tables involved in the operations.
I don't have an experience with PG perf. testing and I guess that
I may need to
Is there a way to force database to load
a frequently-accessed table into cache and keep it there?
Thanks,
Mike.
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
What's the actual distribution of values in these columns?
Are you searching for values that are particularly common
or uncommon?
This column always has a predefined set of values.
Usually the app. would search for one of the
existing values.
---
Total records:
Just want to share in case you want to make a change
in the code, or perhaps tell us that we didn't do the right thing.
At some point we needed to add -DTCL_THREADS and -D_REENTRANT
to the makefiles and then we ran into a problem with pgtcl library.
This seems to be HP specific (HP-11) and
We have customers who prefer to use their backup facilities
instead of what we provide in the app (we use pg_dump)
I hear speed is at least one consideration.
The questions I need to answer are these:
1) Is this absolutely safe to do file copy (cpio, or
smth. else, whatever the robust backup
I'm running Postgres v.7.3.4.
In my database dump file I see this:
CREATE FUNCTION plpgsql_call_handler () RETURNS language_handler
AS '/home/tmichael/build/relipg21/syncinc/lib.sol2/plpgsql',
'plpgsql_call_handler'
LANGUAGE c;
The hardcoded library path may become an obstacle when
updating pg_proc?
Thank you.
Michael Brusser [EMAIL PROTECTED] writes:
I'm running Postgres v.7.3.4.
In my database dump file I see this:
CREATE FUNCTION plpgsql_call_handler () RETURNS language_handler
AS '/home/tmichael/build
.
Michael Brusser [EMAIL PROTECTED] writes:
I'm running Postgres v.7.3.4.
In my database dump file I see this:
CREATE FUNCTION plpgsql_call_handler () RETURNS language_handler
AS '/home/tmichael/build/relipg21/syncinc/lib.sol2/plpgsql',
'plpgsql_call_handler
Interestingly I tried to address the same problem few days ago.
I used pg_dump, grep, etc - in the end I got what I needed, but
it was a cumbersome ordeal.
I think ideally it would be great to have a utility that would
give me a clean diff. between the schemas.
Perhaps pg_dump could have a new
We have a customer who reports a weird problem.
Too often the App. Server fails to connect to the database.
Sometimes the scheduled vacuum fails as well.
The error message is always the same:
FATAL: The database system is shutting down
But from what I see no one is trying to shut down the
I see this code in pg_ctl:
PID=`sed -n 1p $PIDFILE`
if [ $PID -lt 0 ];then
PID=`expr 0 - $PID`
Wnen it is possible (and why) to have a negative number in postmaster.pid?
Thanks,
Mike
---(end of broadcast)---
TIP 7: don't forget
Sorry, I should have checked the source first.
Just found this in miscinit.c :
* By convention, the owning process' PID is negated if it is a standalone
* backend rather than a postmaster. This is just for informational
purposes.
-Original Message-
I see this
Our customer has problems with Pg 7.3.2 on Solaris.
There are numerous errors in the app. server log and in the database log,
including these:
LOG: open of /mnt_c1t2d0s0/some-path/postgresql/pg_xlog/0001
(log file 0, segment 1) failed: No such file or directory
LOG: invalid primary
It looks that No such file or directory followed by the abort signal
resulted from manually removing logs. pg_resetxlog took care of this,
but other problems persisted.
I got a copy of the database and installed it on the local partition.
It does seem badly corrupted, these are some hard errors.
-Original Message-
From: [EMAIL PROTECTED]
pg_dump: ERROR: XLogFlush: request 0/A971020 is not satisfied ---
flushed only to 0/550 ... lost synchronization with
server, resetting
connection
Okay, you have a page with an LSN of A971020 which is past end of XLOG
I have Postgres 7.2.1 configured to listen on TCP/IP port.
When the server starts up it still creates the socket file in /tmp.
Removing this file manually does not seem to cause any problem for the
application.
Is there a way to prevent postmaster from creating this file?
Is this really safe to
For what it's worth, I like the second form better.
Mike
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Christopher
Kings-Lynne
Sent: Sunday, May 23, 2004 6:08 AM
To: PostgreSQL-development
Subject: [HACKERS] Syntax question
Here are the two
Would anybody object to adding an extra line at startup that shows the
version number of the database system?
Message suggestion:
Starting PostgreSQL Version database system
(Nothing cheesy, just informative and neutrally welcoming...)
Comments?
Best Regards, Simon Riggs
If you do
I have an intermittent problem with PostgreSQL 7.3.2 on Solaris 8.
The backend process crashes once in a while, with this in the database log:
... ...
2004-07-05 22:43:54 LOG: database system is ready
IpcSemaphoreInitialize: semctl(id=65615, 14, SETVAL, 0) failed:
Invalid argument
2004-07-06
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Tom Lane
Sent: Sunday, May 25, 2003 9:03 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] vacuum analyze corrupts database
Michael Brusser [EMAIL PROTECTED] writes:
(dbx) where 30
=[1] pfree(0x489420, 0xffbee890
Well, first thing I'd ask is whether the other installation is using
the same locale settings.
Oh, yes, I am very sure of that.
Mike
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Anyone have lists of implementation-defined SQLSTATEs for
the big commercial DBs?
This points to the Oracle docs.
http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a87540/ch2.htm
Table 2-2 SQLSTATE Status Codes
---(end of
Hi, folks;
We're running Postgres 7.3.2.
At the end of some procedure we get a core dump on HP-11.
This does not seem reproducible on Solaris or Linux.
Working with debugger we get this stack:
#0 0xc0185a20 in mallinfo+0x2144 () from /usr/lib/libc.2
(gdb) where
#0 0xc0185a20 in mallinfo+0x2144
Hi, folks;
We're running Postgres 7.3.2 and we have a core dump on HP-11.
This does not seem reproducible on Solaris or Linux.
Working with debugger we get this stack:
#0 0xc0185a20 in mallinfo+0x2144 () from /usr/lib/libc.2
(gdb) where
#0 0xc0185a20 in mallinfo+0x2144 () from /usr/lib/libc.2
#1
We ran into problem while load-testing 7.3.2 server.
From the database log:
FATAL: cannot open /home/some_path/postgresql/PG_VERSION:
File table overflow
The QA engineer who ran the test claims that after server was restarted
one record on the database was missing.
We are not sure what exactly
I wonder how Postgres handles this situation.
(Or power outage, or any hard system fault, at this point)
Theoretically we should be able to recover from this without loss of
committed data (assuming you were running with fsync on). Is your QA
person certain that the record in question
Can somebody clarify for me the requirement for the SHMSEG kernel parameter,
please.
The Postgres doc says:
SHMSEG - Maximum number of shared memory segments per process
only 1 segment is needed, but the default is much higher
I was trying to calculate the kernel parameters for running
We're testing application with Postgres 7.3.2 on the backend.
The entire test involves running series of individual tests.
Few times throughout this procedure the database server is being
shut down and started up again
Normally, this is what I see in the database log.
2003-07-29 10:14:33 [14513]
I'm afraid I'm confused about something very simple... but anyway
I need to run a query on a varchar field containing a backslash.
My first attempt looked like this:
SELECT smth. FROM tbl WHERE situation LIKE '%\\%';
This did not returned any rows.
I looked up for a reference, confirmed that
Env: Postgres 7.3.4 on Unix
I have a script to create a new database user and update pg_hba.conf.
I was wondering whether I need to restart server, or simply run pg_ctl
reload.
The question is what happens to all active clients when all backends get the
signal.
I ran such client process which
Is there something special about function current_user?
In v.7.3.4 it only works when I do select current_user;
and breaks when called with the empty arg. list:
syncdb=# select current_user();
ERROR: parser: parse error at or near ( at character 20
This behavior is just the opposite to that
I wonder if this is feasible to enhance create trigger
so I could say 'create or replace'
Thanks,
Mike.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Yes, we use NFS. Many of our customers use it as well.
Mike.
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
... ...
Michael Brusser [EMAIL PROTECTED] writes:
2003-10-10 22:37:05 ERROR: cannot read block 0 of s_noteimportlinks:
Interrupted system call
Hmm. I
With Pg 7.3.x we initialize database with -E UNICODE option.
I'd like to provide support for automatic conversion to Chinese char-set
by putting client_encoding big5 into postgresql.conf.
But when I try \encoding big5 in psql session I get this:
big5: invalid encoding name or conversion procedure
We integrate PostgreSQL with our product, which we ship to the end user.
We do read the release notes, they are important to us.
They don't have to be excruciatingly long, they can't be
ridiculously short and cryptic.
You have to find the golden spot in the middle. Just treat us
the way you want
-Original Message-
From: Bruce Momjian
...
The big question is whether the current release notes hit he right
balanced. Do they for you?
The last time I read the notes was when we upgraded to 7.3.4.
I'll pick up couple entries from Release Notes and the HISTORY file
(which we always
But this seems to work correctly on 7.3.2 and 7.3.4:
psql -c select round (2.5)
Password:
round
---
3
(1 row)
=
I just tried that on my 7.2.4 and 7.4 beta 4 machines and I get 2 for
round(2.5)
---(end of
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Shouldn't it revert to the default value?
No, not unless you think the postmaster should react to comments in the
postgresql.conf file, which is rather against my idea of a comment.
However, you're not the first to get burnt by this
39 matches
Mail list logo
