"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Sure, but it might be getting delivered to, say, your "sleep" command. You
>> haven't checked the return value of sleep to handle any errors that may
>> occur.
>> As it stands you have to check for errors from e
Gregory Stark <[EMAIL PROTECTED]> writes:
> Sure, but it might be getting delivered to, say, your "sleep" command. You
> haven't checked the return value of sleep to handle any errors that may occur.
> As it stands you have to check for errors from every single command executed
> by your script.
T
On Fri, Nov 17, 2006 at 09:39:39PM -0500, Gregory Stark wrote:
> "Stephen Harris" <[EMAIL PROTECTED]> writes:
> > [...variable setup...]
> > while [ ! -f $wanted_file ]
> > do
> > if [ -f $abort_file ]
> > then
> > exit 1
> > fi
> > sleep 5
> > done
> > cat $wanted_f
"Stephen Harris" <[EMAIL PROTECTED]> writes:
> My script was just a ksh script and didn't do anything special with signals.
> Essentially it does
> #!/bin/ksh -p
>
> [...variable setup...]
> while [ ! -f $wanted_file ]
> do
> if [ -f $abort_file ]
> then
> exit 1
> fi
>
Richard Huxton wrote:
> Matthew Peter wrote:
> > I have DB1 and DB2 pg_databases... I then have a function in DB2 that
> > wants some results from DB1, is it possible to query another db? Like
> > how \! lets you hit the command line... but I need it in plpgsql if
> > possible.
>
> Look into the d
On Fri, Nov 17, 2006 at 05:03:44PM -0500, Tom Lane wrote:
> Stephen Harris <[EMAIL PROTECTED]> writes:
> > Doing a shutdown "immediate" isn't to clever because it actually leaves
> > the recovery threads running
>
> > LOG: restored log file "00010001003E" from archive
> > LOG: receiv
On Fri, 2006-11-17 at 16:42 -0800, Jeremy Smith wrote:
> On 11/17/06, Jeff Davis <[EMAIL PROTECTED]> wrote:
> >
> > Why do you need so many functions though? Won't one SQL function do the
> > trick?
> >
> > Regards,
> > Jeff Davis
> >
> >
>
> You're right, one will do the trick - I was thi
> I am attempting to distribute the fluid from the process table to its
> own table (pipe or equipment) depending on whether the fluid is
> classified as op, ip or eq.
OK, now I understand.
> I didn't include the after insert trigger as there can't be a trigger
> until the ip_op_equipment is upda
On 11/17/06, Jeff Davis <[EMAIL PROTECTED]> wrote:
Why do you need so many functions though? Won't one SQL function do the
trick?
Regards,
Jeff Davis
You're right, one will do the trick - I was thinking update and
delete, but of course those will be fine with plain rules because the
Have you explored the possibility that the trigger is doing what it is
supposed to. I would investigate the procedure that updates the
ip_op_equipment field. Make sure that it is not updating all the rows each
time and thereby firing your trigger for each update. TG_OP is a variable
available t
On Fri, 2006-11-17 at 11:49 -0800, Jeremy Smith wrote:
> Now, the default value for new.id gets evaluated *each time* I
> reference new.id - meaning the rule's first insert sees N for new.id
> while the rule's second insert sees N+1. That is kind of odd - I
> would think that the default value wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/17/06 16:31, Alvaro Herrera wrote:
> Matt Miller wrote:
>> I'd like SYSDATE to work syntactically and semantically the same as
>> CURRENT_TIMESTAMP (or CURRENT_TIME, or whatever). I can create a
>> function called "sysdate" that does the trick,
I am attempting to distribute the fluid from the process table to its own
table (pipe or equipment) depending on whether the fluid is classified as
op, ip or eq.
I didn't include the after insert trigger as there can't be a trigger until
the ip_op_equipment is updated.
BTW what is TG_OP that
On Fri, 2006-11-17 at 15:46 -0500, Wm.A.Stafford wrote:
> If we use '\x05' as suggested by the
> Fastreader User guide. PostgreSQL complains "ERROR: COPY delimiter
> must be a single character".
>
> Any help or suggestions would be appreciated.
\x05, aka control-e, ctl-e, ^e, C-e, etc, is
> When I trigger 'after insert' the function doesn't work because the
> ip_op_equipment condition is an update. When I manually enter directley
> into the table this trigger works fine when both the fluid and
> ip_op_equipment are entered as one entry.
>
> When I trigger 'after update' every row
> Hi all,
>
> I have some doubts about SPI (Server Programming Interface). In
> fact, I must create Stored Procedures in Postgres (8.0). The problem is:
> all stored procedures and, may be, some triggers must be compiled 'cause
> the clients can't access the source code of them.
> To solve
Matt Miller wrote:
> I'd like SYSDATE to work syntactically and semantically the same as
> CURRENT_TIMESTAMP (or CURRENT_TIME, or whatever). I can create a
> function called "sysdate" that does the trick, but then it seems I have
> to reference the function as "sysdate ()," but I want to be able t
Hi All
I have three tables
Create Table Pipe
( pipe_id serial ,
fluid_id int4
) ;
Create Table Equipment
(Equipment_id serial,
fluid_id int4
) ;
Create Table Processes
( Fluid_id serial
fluid varchar (15),
ip_op_equipment varchar (5)
) ;
The interface inserts the name
I'd like SYSDATE to work syntactically and semantically the same as
CURRENT_TIMESTAMP (or CURRENT_TIME, or whatever). I can create a
function called "sysdate" that does the trick, but then it seems I have
to reference the function as "sysdate ()," but I want to be able to get
away with just "sysda
Jaime Silvela <[EMAIL PROTECTED]> writes:
> I do
> delete from staging_deal where staging_deal_id = 1
> and get
> ERROR: update or delete on "staging_deal" violates foreign key
> constraint "staging_deal_fkey" on "staging_document"
> DETAIL: Key (staging_deal_id)=(1) is still referenced from tab
Stephen Harris <[EMAIL PROTECTED]> writes:
> Doing a shutdown "immediate" isn't to clever because it actually leaves
> the recovery threads running
> LOG: restored log file "00010001003E" from archive
> LOG: received immediate shutdown request
> LOG: restored log file "00010
Hi,
On Wed, 2006-11-08 at 17:56 -0700, Leonel Nunez wrote:
> I've seen that the 8.1.5-6 rpms are available.
> Are those RPMs corrected from the announced bug ?
Yes.
Regards,
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development,
Le vendredi 17 novembre 2006 22:07, Wm.A.Stafford a écrit :
> We are trying to load our PostgreSQL DB with data that contains many
> corrupted rows. I recall that sql loader will skip corrupted rows and
> keep going. We are using the PostgreSQL copy command to load and it
> just gives up when
Wm.A.Stafford wrote:
We are trying to load our PostgreSQL DB with data that contains many
corrupted rows. I recall that sql loader will skip corrupted rows and
keep going. We are using the PostgreSQL copy command to load and it
just gives up when the first corrupted row is encountered.
T
Hi,
Le vendredi 17 novembre 2006 21:46, Wm.A.Stafford a écrit :
> We can not figure out
> how to specify a non-printing character for the delimiter in the
> PostgreSQL copy command. If we use '\x05' as suggested by the
> Fastreader User guide. PostgreSQL complains "ERROR: COPY delimiter
> must
We are trying to load our PostgreSQL DB with data that contains many
corrupted rows. I recall that sql loader will skip corrupted rows and
keep going. We are using the PostgreSQL copy command to load and it
just gives up when the first corrupted row is encountered.
Thanks in a advance,
-=
In case anybody was thinking of spending time on this:
The problem was the existence of a table of the same name in a different
schema.
ERROR: update or delete on "staging_deal" violates foreign key
constraint "staging_deal_fkey" on "staging_document"
should have in fact pointed to "doclib
We are having trouble coming up with a column separator for the Oracle
data that is being imported into our PostgreSQL DB. We are using
Fastreader to dump Oracle tables. We then use PostgreSQL copy to load
the table data into PostgreSQL. Unfortunately, some of the Oracle data
contains ev
I'm finding a strange sort of 'zombie' table behavior.
I try to delete a row of a database that used to be referenced by a
table that has now been deleted.
I do
delete from staging_deal where staging_deal_id = 1
and get
ERROR: update or delete on "staging_deal" violates foreign key
constraint
I'm using 8.2beta3 but I'm asking here before posting to the devel
lists as suggested by that lists guidelines..
First the question, because it might be simple and I'm stupid. However
I'll then go into detail in case I'm not so silly.
In a database which is in recovery mode waiting on an externa
am Fri, dem 17.11.2006, um 17:22:47 -0200 mailte Leodinei Bielak folgendes:
> Hello. I'm using PostgreSQL 8.1.4 with WinXP Sp2.
> The acess over network 100mbit is too slow.
> My query take 100 times more.
How long is a long time?
> The use of CPU and network is low, less than 1%.
> Searching
On 11/16/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Actually, the best way to do that is to attach a default to the view
itself.
CREATE VIEW v AS SELECT ... ;
CREATE RULE ... for insert on v ... ;
ALTER TABLE v ALTER COLUMN c DEFAULT whatever;
In this formulation the rule
hi mike
you seem to have run into the same (or similar) bug as i did with 8.2 (also
w2k3 here)
I have noticed that in the event logs that I am again seeing errors about
the renaming:
LOG: could not rename file
"pg_xlog/000100690021" to "pg_xlog/000100690030"
continui
Hello. I'm using PostgreSQL 8.1.4 with WinXP Sp2.
The acess over network 100mbit is too slow.
My query take 100 times more.
The use of CPU and network is low, less than 1%.
Searching in the web I found other with the same problem, but no reply to
resolve this problem.
The query is a simple "SELE
I've just gotten a dump from pgMyAdmin for a production database that i
wanted to update the dev db with. However, i'm seeing a multitude of
errors. From what i can see, the columns are mixed up in the COPY block
for a particular table. My guess is that a tab character has thrown
everything int
> > Does this message in application.log can be the source of problem
> >
> > wuaueng.dll (1204) Synchronous read page checksum error
> -1018 ((1:801
> > 1:801) (0-13218) (0-14642)) occurred. Please restore the databases
> > from a previous backup.
>
> I don't recognise this as a PostgreSQL err
Ardian Xharra wrote:
Does this message in application.log can be the source of problem
wuaueng.dll (1204) Synchronous read page checksum error -1018 ((1:801
1:801) (0-13218) (0-14642)) occurred. Please restore the databases from
a previous backup.
I don't recognise this as a PostgreSQL error
Clarence Gardner <[EMAIL PROTECTED]> writes:
> I'm still creeping up on the problem. I configured postgres to resolve
> a deadlock only after a month, and now I seem to have a complete
> snapshot of one of them.
If you don't mind rebuilding Postgres from source, here's the patch
as applied to 8.1
Does this message in application.log can be the source of problem
wuaueng.dll (1204) Synchronous read page checksum error -1018 ((1:801 1:801)
(0-13218) (0-14642)) occurred. Please restore the databases from a previous
backup.
Regards Ardian,
- Original Message -
From: "Richard Huxt
"James Moss" <[EMAIL PROTECTED]> writes:
> I could use a helpful suggestion or two as to why the following is
> occuring or more to the matter, how I might work around it. Certainly
> appears to be a bug or some sort of misunderstanding on my part.
The content of a text datum is not guaranteed nu
I could use a helpful suggestion or two as to why the following is
occuring or more to the matter, how I might work around it. Certainly
appears to be a bug or some sort of misunderstanding on my part.
This has been tested on FreeBSD/i386 5.4 and postgres 8.1.3 as well as
Linux (2.4 kernel) and
Hi,
how to make UDF visible on cluster (for all databases)?
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Thanks to you and Russell -- the iconv trick had eluded me for some reason.
Serious pain on such a large file, but at least it works (test of the small 22
gig sample)! A little splitting, a little converting, some diff-ing, reassmbly
and load. piece o' cake!
Thanks again ... sorry for wasting b
Richard Huxton a écrit :
Arnaud Lesauvage wrote:
Richard Huxton a écrit :
Arnaud Lesauvage wrote:
Hi all !
I am trying to exclude just one schema of my dump.
pg_dump -N myschema
or
pg_dump --exclude-schema=myschema
both tell me that the option is unknown.
It's not in 8.1 - you must have be
thanks a lot i followed your instruction i have put the 32 bit libpq.so.4 in a
separate folder which is pointed to by
LD_LIBRARY_PATH
and the exe functions.
thanks,
regards
Surabhi
From: Albe Laurenz [mailto:[EMAIL PROTECTED]
Sent: Fri 11/17/2006 3:12 PM
To: s
Arnaud Lesauvage wrote:
Hi all !
I am trying to exclude just one schema of my dump.
pg_dump -N myschema
or
pg_dump --exclude-schema=myschema
both tell me that the option is unknown.
It's not in 8.1 - you must have been reading the 8.2 docs
http://www.postgresql.org/docs/8.1/static/app-pgdump.
On Thu, Nov 16, 2006 at 06:23:23PM -0700, Jim Nasby wrote:
> Well, for tables it wouldn't be hard to craft a query that spits out
> the appropriate ALTER TABLE RENAME statements. Unfortunately, ALTER
> TABLE doesn't support renaming columns, but it might be safe to run
> an update on the syst
> If you have it set to less than the time needed to do a vacuum, then
> yes, autovac will fail. You expected differently? Do you think it's
> a good idea for autovac to ignore statement_timeout? (Maybe it is,
> but I suspect we'd get complaints about that too.)
>
"alter role set statement_time
Ardian Xharra wrote:
For the column: date(varchar 8) '2000606' the
SELECT ascii(substring(date,4,1)) from jnlsale WHERE id_jnlsale=28384
gives: 22
SELECT ascii('6'); gives 54
Hmm - a difference of 32, or a single bit (2^5).
For the column: amount(float 8) 1.20932764209866e-307 the
SELECT as
> let me explain with an example
> say i have a 32 bit exceutable called Installer
>
> it dynamically links to 4 libraries which are called:
> libdbx1, it is dependent on (ROOT)/postgres/arch/$(ARCH)d/lib -lpq
(specified in the makefile)
> libdbx2, it is also dependent on (ROOT)/postgres/arch/$(A
Hi all !
I am trying to exclude just one schema of my dump.
pg_dump -N myschema
or
pg_dump --exclude-schema=myschema
both tell me that the option is unknown.
I am using the win32 binary distribution v8.1.4 (pg_dump
--version says 8.1.4 too).
Is this normal ?
Thanks !
--
Arnaud
hi,
let me explain with an example
say i have a 32 bit exceutable called Installer
it dynamically links to 4 libraries which are called:
libdbx1, it is dependent on (ROOT)/postgres/arch/$(ARCH)d/lib -lpq (specified
in the makefile)
libdbx2, it is also dependent on (ROOT)/postgres/arch/$(ARCH)
52 matches
Mail list logo
