"Fernando Hevia" <[EMAIL PROTECTED]> writes:
> With 8.2.x the ARST abbreviation was recognized after including the
> following line in /usr/share/postgresql/8.2/timezonesets/Default
> ARST -14400 D # Argentina Summer Time
Um ... is that really offsetting in the correct direction? What I put
i
> Tom Lane [mailto:[EMAIL PROTECTED] wrote:
>
> Since the OP has apparently already managed to get updated tzdata files
> installed on his system, he could just copy them into
> /usr/share/postgresql/timezone --- anything using zic should be a
> compatible file format.
>
> The lack-of-ARST-on
On Thu, 2008-01-03 at 19:17 -0500, Geoffrey wrote:
> Ow Mun Heng wrote:
> > However during the startup of slony, I noticed that it issues a truncate
> > command to the (to be) replicated table. Hence, this means that there's
> > no such need for me to do a dump/restore in the 1st place.
> >
> Thi
Dan Langille <[EMAIL PROTECTED]> writes:
> What error code would be raised for a duplicate index name?
regression=# \set VERBOSITY verbose
regression=# create table t1 (f1 int);
CREATE TABLE
regression=# create index t1i on t1(f1);
CREATE INDEX
regression=# create index t1i on t1(f1);
ERROR: 42P0
"George Pavlov" <[EMAIL PROTECTED]> writes:
> I started seeing some negative durations in my production query logs --
> a "-" sign preceding the duration number, e.g.:
> % grep 'duration: -' postgresql-Wed-*
> postgresql-Wed-09.log:2008-01-02 08:56:33 PST [11705]: [538-1] LOG:
> duration: -268280.
Hi folks,
With reference to:
http://www.postgresql.org/docs/8.2/interactive/errcodes-appendix.html
What error code would be raised for a duplicate index name?
I didn't see anything appropriate. Possibly: 42710 DUPLICATE OBJECT
thanks
--
Dan Langille - http://www.langille.org/
BSDCan - The Te
Ow Mun Heng wrote:
{resend as don't see it on the list after 4 hours}
I'm just wetting my hands with slony and during the setup of the slave,
I did and dump and restore of the master DB to the Slave DB.
You don't need to do this.
However during the startup of slony, I noticed that it issues
I started seeing some negative durations in my production query logs --
a "-" sign preceding the duration number, e.g.:
% grep 'duration: -' postgresql-Wed-*
postgresql-Wed-09.log:2008-01-02 08:56:33 PST [11705]: [538-1] LOG:
duration: -268280.421 ms
postgresql-Wed-15.log:2008-01-02 15:01:01 PST [
I wish to enable server instrumentation for pgadmin3 on a CentOS-5 box
running the stock PostgreSQL 8.1.9 installed via yum. Can someone tell me
where I get the necessary support files and scripts for CentOS to
accomplish this? I installed postgres-contrib but cannot find a script
called admin81.s
[EMAIL PROTECTED] (Bruce Momjian) writes:
>> I am not sure if I am asking too much but does it make sense, and is it
>> possible, to enhance NOTIFY that process "name/value" pair? Like this:
>>
>> NOTIFY "MyName=MyValue";
>>
>> With the capability of name/value pair, the listener will not have to
Alvaro Herrera wrote:
> Andreas 'ads' Scherbaum wrote:
>
> > It is possible, that some notifies, if following in a very short time
> > frame, can get lost.
> >
> > In case we want to send extra text messages with NOTIFY, we should make
> > sure, that no notify get lost.
>
> Right. Currently, NO
Andreas 'ads' Scherbaum wrote:
> It is possible, that some notifies, if following in a very short time
> frame, can get lost.
>
> In case we want to send extra text messages with NOTIFY, we should make
> sure, that no notify get lost.
Right. Currently, NOTIFY acts like Unix signals -- consecuti
Andreas 'ads' Scherbaum wrote:
> > > With the capability of name/value pair, the listener will not have to
> > > check notification details by reading tables.
> >
> > TODO already has:
> >
> > * Add optional textual message to NOTIFY
> >
> > This would allow an informational messag
Hello,
On Thu, 3 Jan 2008 11:21:37 -0500 (EST) Bruce Momjian wrote:
> > I am not sure if I am asking too much but does it make sense, and is it
> > possible, to enhance NOTIFY that process "name/value" pair? Like this:
> >
> > NOTIFY "MyName=MyValue";
> >
> > With the capability of name/value
>Sebastián Baioni wrote:
Every day we run a Windows Programmed pg_dump, it used to
work fine with PostgreSQL 8.0, but since we installed the new
version we are not able to make a backup. We tried to make a
whole database backup and it never ends. We tried to backup
tab
"Harald Armin Massa" <[EMAIL PROTECTED]> writes:
> Within the PostgreSQL-Documentation for 8.2,
> http://www.postgresql.org/docs/8.2/interactive/xfunc-c.html, still I
> find:
> """Using call conventions version 0, we can define c_overpaid as:"""
> That sound very tutorial-like; and so $I wonder:
> I am not sure if I am asking too much but does it make sense, and is it
> possible, to enhance NOTIFY that process "name/value" pair? Like this:
>
> NOTIFY "MyName=MyValue";
>
> With the capability of name/value pair, the listener will not have to
> check notification details by reading tables.
Dear developers,
With the existing single-notification-value mechanism, not only
SELECT'ing tables are necessary in some cases but DELETE'ing rows and
synchronizing the DELETE are also required in many cases where there are
multiple client connections to the same database.
As an example, supposin
Hello
version 0 Calling Convention is really deprecated. From 8.2 manual:
We present the "old style" calling convention first — although this
approach is now deprecated, it's easier to get a handle on initially.
Regards
Pavel Stehule
On 03/01/2008, Harald Armin Massa <[EMAIL PROTECTED]> wrote:
Please, don't top post!
Sebastián Baioni wrote:
>>> Every day we run a Windows Programmed pg_dump, it used to
>>> work fine with PostgreSQL 8.0, but since we installed the new
>>> version we are not able to make a backup. We tried to make a
>>> whole database backup and it never ends. We tried
Also are there any better ways to debug tcl scripts in postgres?
I've just noticed the script I'm using (and the one on the example
site) works for a single row delete, but not for more than 1 row.
It's hard to see from the error given in postgres what's going off.
E.g.
DELETE FROM "MYTABLE" WHE
Hello,
I am researching information about writing C-language-Functions for
PostgreSQL. I came accross the slides of an OSCON 2004 tutorial of
Joe Conway
http://www.joeconway.com/tut_oscon_2004.pdf
where he states:
Version 0 Calling Convention
• Deprecated
• Has been since the 7.1 release.
• Don'
On Jan 3, 2008, at 5:59 AM, Sebastián Baioni wrote:
I don't have any table called pg_locks in pg_catalog.
We let running pg_dump 8.2.5 at 1:30 AM after an automatic reboot
of the PostgreSQL service and it didn't finish. When I came to the
office at 9:00 there were a lot of locks, but all of
In response to Ow Mun Heng <[EMAIL PROTECTED]>:
>
> I'm just wetting my hands with slony and during the setup of the slave,
> I did and dump and restore of the master DB to the Slave DB.
>
> However during the startup of slony, I noticed that it issues a truncate
> command to the (to be) replicat
Hi people,
Are any of you lot handy with pgtcl then? Or should I be posting on
another list, the only other list I could possible see was
pgsql-hackers?
I managed to modify the tcl script at the address I posted below to
save the field I wanted it to. However I've still not managed to get
it to s
On Tue, 01 Jan 2008, Chuck wrote:
> I'm not sure how to "make sure automatic updates are turned on" as
> Tometzky recommended. Is that a yum setting?
You need to install and configure "yum-updatesd" to perform automatic
updates for you. I don't use it so I don't know exactly how to do
this, but I
I've read through some solutions proposed on ml, blogs etc... but
maybe something changed or someone came up with a better idea or just
I wasn't able to find a satisfactory solution through google...
Of course PHP arrays can't be passed directly to pg functions so:
I can:
1) write a php function
I don't have any table called pg_locks in pg_catalog.
We let running pg_dump 8.2.5 at 1:30 AM after an automatic reboot of the
PostgreSQL service and it didn't finish. When I came to the office at 9:00
there were a lot of locks, but all of them were from the pg_dump conection.
Thanks
Sebast
{resend as don't see it on the list after 4 hours}
I'm just wetting my hands with slony and during the setup of the slave,
I did and dump and restore of the master DB to the Slave DB.
However during the startup of slony, I noticed that it issues a truncate
command to the (to be) replicated table.
29 matches
Mail list logo