Hi Every Body,
i'v declared my trigger function with plpgsql.
there's problems with statements inside IF .. END IF
block that not executed at all.
i guess from plpgsql problem so i registering
procedural language that more friendly to me, thereis
plpython/plpythonu, but the problem rise again.
Hi Every Body,
i'v finished creating function generate_sjno(str_no
char(12), int_reset int2).
when it called an error message raised, this is the
illustration:
baisdb=> select generate_sjno('20060130',6);
ERROR: function generate_sjno("unknown", integer)
does not exist
HINT: No function matche
Hi Every Body,
i have plan to porting my existing projects from MSSQL
Server 2000 to PostgreSQL, but
i'v got several problems with pgoledb when i use it
with Ado component in delphi.
1. is schema displaying not supported on pgoledb,
because when i used zeos (open source dbc component)
they can
Thank you Tom,To the point, fast, and accurate... Much appreciated.Regards,Francois2006/2/18, Tom Lane <[EMAIL PROTECTED]
>:"=?ISO-8859-1?Q?Fran=E7ois?=" <
[EMAIL PROTECTED]> writes:> if I try at the command line to start the service:>> service postgresql start> I get:>> unrecognized serviceLookin
"=?ISO-8859-1?Q?Fran=E7ois?=" <[EMAIL PROTECTED]> writes:
> if I try at the command line to start the service:
>> service postgresql start
> I get:
>> unrecognized service
Looking at the Fedora "service" script, it seems to want the target file
to not only exist but be executable:
if [ -x "${SERV
Paul Vogel <[EMAIL PROTECTED]> writes:
> So something is
> apparently different between the command line "createdb" command and the
> "create database" command.
Not a lot ... createdb just runs psql to issue a create database
command. One possibility is that you gave createdb a mixed-case
datab
I meant WILL not happen again :).Sorry again.On 2/13/06, Tsirkin Evgeny <[EMAIL PROTECTED]> wrote:
I apologize about the case - it was my *administration* fault and would not happenagain.There
is no need to black list - it just would not happen.Sorry.On 2/11/06,
Tom Lane <[EMAIL PROTECTED]> wrote
I apologize about the case - it was my *administration* fault and would not happenagain.There is no need to black list - it just would not happen.Sorry.On 2/11/06,
Tom Lane <[EMAIL PROTECTED]> wrote:This is the second time in the past few days that
lechlecha.jct.ac.ilhas injected a bunch of old m
Hi all,
I'm testing different configurations of postgresql 8.1 running on
debian. The method I was following was:
- change the postgresql.conf
- restart postgres (/etc/init.d/postgresql restart )
- execute my test queries
I have noticed that this is not enough to flush the cache, I do
Hi all,
Which is the best filesystem in linux for postgresql? nowadays I'm
using ext3, I don't know if other filesystems like XFS, reiser... would
be better from the performance point of view.
Cheers!
--
Arnau
---(end of broadcast)---
TIP 1:
I have a pg_dump of a database (without autocreation lines) that I
tried loading by using the commands:
createdb -T template0 -U postgres database; psql -U postgres
database < filename
I couldn't get it to connect via ODBC. But when I added the following
lines in the source file:
CR
Hi,Just upgraded postgresql to 8.1.3, and successfuly configured, started and stopped the RDBMS. One thing I just couldn't do: postgresql as a service on FC3.I copied and renamed this script: postgresql-8.1.3
/contrib/start-scripts/linux to : /etc/rc.d/init.d/postgresql and followed the instructi
Andy Shellam wrote:
Hi,
> As for digging through xlog.c, I'm not a C programmer so I'll stay right
> out of the way - leave that to you guys!!
You don't need to be a C programmer -- just read the code commentary.
It's easy to follow most of the time.
--
Alvaro Herrera
Hi Tom,
Many thanks for the reply. I dug through the log files and found that
the archiving had been failing, so it stands a good chance I'd pulled
1B out of the xlog directory ahead of time.
Over the course of the weekend (once I've upgraded to v8.1.3) I'll try
the exercise again and see wha
Andy Shellam <[EMAIL PROTECTED]> writes:
> Note there are plenty more files ready to run in the archive, and the
> contents of the backup label only mention 1A as the final WAL file of
> the backup, so it is starting to read the next WAL file, but stopping
> for some reason. Is it because of th
"Gregory S. Williamson" <[EMAIL PROTECTED]> writes:
> What's odd is that I have *for sure* fixed the offending entries in the
> source table, but when I do a pg_dump they're back like the proverbial bad
> penny in the dump file.
Sounds to me like you're not dumping the same database that you're
Announcement regarding GBorg project citext (Case-Insensitive text data
type)
http://gborg.postgresql.org/project/citext/projdisplay.php
A new release of the this project is available.
Fixed bugs in functions citext_larger and citext_smaller which were both
overwriting the original arguments with
Tom, et. al.,
pg_dump was not the issue as you surmised. Bad data, fixed in some cases in the
original db and in some cases with a sed script. I tried a pg 8.1 pg_dump and
that in fact helped diagnose the (human) error.
Thanks once again for the help.
gsw
-Original Message-
From: T
I'm trying to
set up WAL archiving on my server, and replicate my live database to a
hot-spare server using online backups.
However, the postmaster on the hot-spare is stopping too early during
the recovery.
In my archived xlog folder on the live server, I have the following
xlogs (note the ba
Thanks for the suggestion -- I'll try the iconv search and see.
What's odd is that I have *for sure* fixed the offending entries in the source
table, but when I do a pg_dump they're back like the proverbial bad penny in
the dump file.
Certainly a reason for migrating, regardless of how painful
20 matches
Mail list logo
