If I turn off fsync on 7.1 does that mean that the wal file is sync'd
(according to WAL_SYNC_METHOD in the log file) and other files are not?
Or does fsync apply to all file equally?
--
Joseph Shraibman
[EMAIL PROTECTED]
Increase signal to noise ratio. http://www.targabot.com
In /usr/local/pgsql/doc/html/runtime-config.html:
DEBUG_PRINT_PARSE (boolean), DEBUG_PRINT_PLAN (boolean),
DEBUG_PRINT_REWRITTEN (boolean), DEBUG_PRINT_QUERY
(boolean),DEBUG_PRETTY_PRINT (boolean)
For any executed query, prints either the query, the parse tree,
the execution plan, or the q
If there's one or more indexes on a table that gets TRUNCATEd, are those
indexes automatically updated as expected from INSERTs and DELETEs?
--
Eugene Lee
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
htt
Fran Fabrizio <[EMAIL PROTECTED]> writes:
> Another crucial piece of information is that each insert kicks off a
> trigger. I did not write the trigger, and do not know how to write
> triggers, but I think that might be the contributing factor to the
> slowness.
Bingo. Your trigger is adding fo
On Mon, 30 Apr 2001, Randall Perry wrote:
> Got a simple PgSQL database running on a linux server which I need the
> client to access for inserts and updates from a Win box.
>
> What's the simplest way to do this; using PHPPgAdmin, or MS Access via ODBC?
>
> Where can I find detailed info on us
lower('blah.blah.mydomain.com'),lower('foo'),lower('bar'),lower('blah'),upper('Me'),
upper('Myself'), upper('I'), upper('INFO'), 'String Here', '20010430
16:00:00')
Pretty straightforward. Table log looks like:
No, I have a redhat 6.x system and I built the postgres myself from the
7.0.3 source.
Tom Lane wrote:
>
> Joseph Shraibman <[EMAIL PROTECTED]> writes:
> > psql:dumpall-2001-4-27:8452: ERROR: copy: line 8933, Bad timestamp
> > external representation '2001-01-17 19:37:60.00-05'
>
> Are you on M
John Coers <[EMAIL PROTECTED]> writes:
> Does a COPY FROM block? In case I am using the wrong terminology,
> what I need to know is if I have multiple clients performing COPY FROM...PQputline()
> using asynchronous connections, will I lose data?
No.
> Will the server simply execute them seriall
David Pieper wrote:
>
> I'm trying to build 7.1 from source on a RedHat box.
> Here's what I keep ending up with:
>
> [root@dp1 postgresql-7.1]# gmake
> gmake -C doc all
> gmake[1]: Entering directory `/opt/src/postgresql-7.1/doc'
> gmake[1]: Nothing to be done for `all'.
> gmake[1]: Leaving dir
Does a COPY FROM block? In case I am using the wrong terminology,
what I need to know is if I have multiple clients performing COPY FROM...PQputline()
using asynchronous connections, will I lose data? Will the server simply execute
them serially?
---(end of broadcast)---
David Pieper wrote:
>
> I'm trying to build 7.1 from source on a RedHat box.
> Here's what I keep ending up with:
>From the gcc version it appears you are on a RedHat 6.x box.
> It seems like I'm missing something, but what?
kernel-headers?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-
Joseph Shraibman <[EMAIL PROTECTED]> writes:
> psql:dumpall-2001-4-27:8452: ERROR: copy: line 8933, Bad timestamp
> external representation '2001-01-17 19:37:60.00-05'
Are you on Mandrake by any chance? Looks like your 7.0 installation
had that infamous roundoff problem.
I recommend manually c
I just updated to 7.1 and tried to restore my database that was dumped
with 7.0.3
psql:dumpall-2001-4-27:8452: ERROR: copy: line 8933, Bad timestamp
external representation '2001-01-17 19:37:60.00-05'
psql:dumpall-2001-4-27:8452: PQendcopy: resetting connection
CREATE
CREATE
[root@d1 /var/lib/
You should be using gmake instead of make.
./configure
gmake
gmake install
Mike
> I am running OpenLinux 2.3 (Caldera) out of the box. Trying to install
> PostGreSQL I seem to be unable to get past the 'make' process. Errors I
> get at the end of the process are:
>
> make[3]: *** [pg_backup_c
I'm trying to build 7.1 from source on a RedHat box.
Here's what I keep ending up with:
[root@dp1 postgresql-7.1]# gmake
gmake -C doc all
gmake[1]: Entering directory `/opt/src/postgresql-7.1/doc'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `/opt/src/postgresql-7.1/doc'
g
Michelle Murrain <[EMAIL PROTECTED]> writes:
> And of course, part of what is going on is that it's really hard to
> debug, since DBI is not returning the full error string, so it's hard
> to know what's going on.
You could look in the postmaster's log (you are keeping one I trust ;-))
to find th
Al <[EMAIL PROTECTED]> writes:
> I am running OpenLinux 2.3 (Caldera) out of the box.
Caldera has an extremely ancient zlib installed. Either update to a
more recent zlib, or manually undefine HAVE_LIBZ in src/include/config.h
after running configure. (7.1.1 will be less trusting about whether
Hi,
What package do you have downloaded ? You need the full install not just
the base package.
Regards,
Gilles
Al wrote:
> I am running OpenLinux 2.3 (Caldera) out of the box. Trying to install
> PostGreSQL I seem to be unable to get past the 'make' process. Errors I
> get at the end of the
Hi,
I widly use DBI/DBD::Pg and doesn't notice any problem. Perhaps because
there's no error or they are well handled :-)). I'm interested to know more
about this problem because I have many script to review in that case.
Could you please send more explanation of the problem and some source code
I am running OpenLinux 2.3 (Caldera) out of the box. Trying to install
PostGreSQL I seem to be unable to get past the 'make' process. Errors I
get at the end of the process are:
make[3]: *** [pg_backup_custom.o] Error 1
make[3]: Leaving directory `/addon/postgresql-7.1/src/bin/pg_dump'
make[2
"Fred Ingham" <[EMAIL PROTECTED]> writes:
> After dropping and recreating the indexes I have (in KB):
Ah, that's more like it.
> So, it appears that I am running into the pathological case.
Actually, a simpler explanation would be if you'd done a bunch of
updates and/or deletes at some point.
I recently posted this on the admin list and got no response. Could
anyone here help me?
Hi,
I am non a "real" sysadmin or dba, but "got stuck" doing it and am trying to learn
via a fairly
difficult problem that my group must deal with: a LARGE volume of data. I have been
working
from
"Jose Norberto" <[EMAIL PROTECTED]> writes:
> I want to make a pg_dump of a database, but I must be sure that no one is
> logged in.
Why?
pg_dump will return a consistent state of the database even if other
transactions are proceeding meanwhile.
regards, tom lane
-
Tom,
Again, thank you for your quick and knowledgeable assistance.
After dropping and recreating the indexes I have (in KB):
oldnew
PostgreSQL pinndex_seq 8 8
pinndx 7,856 7,856
pinndx_pkey 6,984 6,984 (did not recreate)
> This is hard to believe.
i don't want to believe it. trust me.
> I am not sure that "if not found" means anything after a "select max()"
> query. The select will always return exactly one row --- even if it's
> just a NULL --- so I'd expect the "if not found" never to succeed.
> Perhaps you
On Monday 30 April 2001 02:37 pm, Jose Norberto wrote:
> Hello all!
> I want to make a pg_dump of a database, but I must be sure that no one is
> logged in. Which is the best way to do it?
> Thanks in advance
Change the permissions in the pg_hba.conf file
(/usr/local/pgsql/data/pg_hba.conf is th
I recently upgraded from 6.5 to 7.1, and it mostly went smoothly (fixed the
PHP problem, thanks to a list member). But now some of my perl stuff is being
a bit strange, and I'm wondering whether other folks have noticed strangeness
when they upgraded their Postgres as well as upgraded to the ne
Hello all!
I want to make a pg_dump of a database, but I must be sure that no one is
logged in. Which is the best way to do it?
Thanks in advance
_
Get your FREE download of MSN Explorer at http://explorer.msn.com
-
I notice in 7.1, there is a chr() command which converst an intenger
into a char, but it doesn't seem to work in 7.03. Is there an
equivalent command? I couldn't find anything in the docs.
---(end of broadcast)---
TIP 1: subscribe and unsubscrib
"Thomas F. O'Connell" <[EMAIL PROTECTED]> writes:
> now, this function works for existing records in the table
> significant_records. but as i add records, i end up having to drop and
> recreate the function in order for it to record the existence of the new
> records.
This is hard to believe.
are there circumstances under which a pl/pgsql function will cache the
contents of a view?
i can do this sequence of actions just fine:
create table foo (
id int2 primary key
);
create view foo_view as
select *
from foo;
create function get_new_foo() returns int2 as '
declare
"Fred Ingham" <[EMAIL PROTECTED]> writes:
> PostgreSQL pinndex_seq 8
> pinndx 7,856
> pinndx_pkey 6,984
> parent_ndx 6,952
> tagpath_ndx 5,552
> tagname_ndx 5,560
> atrname_ndx 5,696
> pinnum_ndx
32 matches
Mail list logo
