> > > > It checks for a '\' followed by three digits, but does not attempt
to
> > > > enforce that the three digits actually produce a valid octal number.
> > Anyone
> > > > object to me fixing this?
> > > >
> >
> > Based on the thread this morning on patches, I was thinking we should
allow
> > '\
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Is the schedule still to go beta Monday?
Well, I dunno about you, but I've had a few distractions to deal with
over the past couple days ;-)
I'll keep trying to clean up loose ends, but I wonder if we should put
it off a few days more. There's still a
Oh, I see. Can you send an detailed email to hackers to Tatsuo can get
it fixed? If we have to back it out, we will.
Monday is not written in stone. If people want it later, we can do
that. Having it compile is a beta requirement. :-)
> * Bruce Momjian <[EMAIL PROTECTED]> [010906 23:40]:
* Bruce Momjian <[EMAIL PROTECTED]> [010906 23:40]:
> Is the schedule still to go beta Monday?
I would object based on the bug I just sent. the last multi-byte
stuff doesn't compile (the file is there now...) ...
LER
>
> --
> Bruce Momjian| http://candle.pha.pa.us
This commit doesn't compile...
With configure input:
CC=cc CXX=CC ./configure --prefix=/usr/local/pgsql --enable-syslog \
--with-CXX --with-perl --enable-multibyte --enable-cassert \
--with-includes=/usr/local/include --with-libs=/usr/local/lib \
--enable-debug \
[EMAIL PROTECTED] writes:
> My pattern of use for ``CREATE RULE... NOTIFY...'' was, up to now, to get
> a notice when anything changed on a table and then go look what happened;
> a `poor man's statement level trigger' if you wish. Thus, the old behavior
> didn't bother me that much. I don't know
Is the schedule still to go beta Monday?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup.| Drexel Hill, Pennsylvania 19026
> > > It checks for a '\' followed by three digits, but does not attempt to
> > > enforce that the three digits actually produce a valid octal number.
> Anyone
> > > object to me fixing this?
> > >
>
> Based on the thread this morning on patches, I was thinking we should allow
> '\\', '\0', or '\
>
> Should be fixed. I noticed this myself. Should we require three digits?
>
>
> > I just noticed some unexpected behavior from byteain:
> >
> >
> > test=# select '\\009'::bytea;
> > ?column?
> > --
> > \011
> > (1 row)
> >
> > It checks for a '\' followed by three digits, but does
"Joe Conway" <[EMAIL PROTECTED]> writes:
> It checks for a '\' followed by three digits, but does not attempt to
> enforce that the three digits actually produce a valid octal number. Anyone
> object to me fixing this?
Clearly a bug. Fix away...
regards, tom lane
--
Should be fixed. I noticed this myself. Should we require three digits?
> I just noticed some unexpected behavior from byteain:
>
> test=# select '\\009'::bytea;
> ?column?
> --
> \011
> (1 row)
>
> test=# select '\\444'::bytea;
> ?column?
> --
> $
> (1 row)
>
> test=#
I'd just like to reassure everyone that the projects currently hosted
by greatbridge.org will be taken care of; there's no need for people to
scramble around looking for new sites.
The physical hosting will be picked up by hub.org. We still have to
work out what the site name will be and the det
I just noticed some unexpected behavior from byteain:
test=# select '\\009'::bytea;
?column?
--
\011
(1 row)
test=# select '\\444'::bytea;
?column?
--
$
(1 row)
test=# select '\\999'::bytea;
?column?
--
\221
(1 row)
The reason is the following code in byteain:
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Plus, since it's is 100% backwards compatible with the version in 7.1.2, you
> might want to back port it to the 7.1.* branch?
Since we're hoping to go beta with 7.2 next week, I doubt there will be
any further releases in the 7.1.* branch.
Well, the FTI code that was committed works perfectly - it compiles fine
against 7.0.3 and 7.1.2 and is in use indexing 2 columns in 2 row tables
in two production and one test servers.
The updated fti.pl we submitted still uses the PGConnect style functions,
rather than the PG::Connect style
Yeah, I use FreeBSD's wonderful newsyslog utility, and I do my logging like
this:
su -l pgsql -c '[ -d ${PGDATA} ] && exec /usr/local/bin/pg_ctl
start -s -w -o "-i" -l /var/log/pgsql.log'
And my /etc/newsyslog.conf entry:
/var/log/pgsql.log pgsql:pgsql 600 3 4096 * Z
Chris
>
Hi Darren,
I'd be interested in finding out what your usage stats are, and any
requirements for hosting the replication content.
As qualification, we maintain an infrastructure at GlobalCentre (a child
company of http://www.exodus.com/ ) This hosting facility also serves
http://www.yellowpages.c
Is this something that still needs fixing?
> > I believe the reason for this is that in Read Committed mode,
> > each separate query from the client computes a new snapshot (see
> > SetQuerySnapshot calls in postgres.c). So, when your
> > "select ctid, i from t1" query executes, it computes a
Hey dudes, sorry. I am sad to see it go.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Peter Harvey wrote:
>Yes. But pgsql does not support multiple inheritance (from what I can
>tell)...
In fact it does:
create table child (col1 text) inherits (parent1, parent2);
Identically named and typed columns in the parents are merged.
--
Oliver Elphick
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Has this been addressed?
IIRC, I looked at the patch and decided it was okay.
regards, tom lane
>> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> The latest patch we submitted to the fulltextindex module improved lots
Added to TODO.detail/transactions as a nested transaction idea.
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > >> The complaints about WAL size amount to "we don't have the disk space
> > >> to keep track of this, for long-running transactions". If it doesn't
> > >> fit on disk, how likely i
Yes, I think this is broken because a multi-byte commit failed to add
some files. I have contacted Tatsuo about this.
> With the following configure script:
>
> CC=cc CXX=CC ./configure --prefix=/usr/local/pgsql --enable-syslog \
> --with-CXX --with-perl --enable-multibyte --enable-cass
[EMAIL PROTECTED] writes:
> versuch=# CREATE RULE ru_u_chkntfy AS ON UPDATE TO chkntfy DO NOTIFY CHKNTFY;
> CREATE
> versuch=# update chkntfy set nummer=10 where nummer = 1;
> ERROR: Conditional NOTIFY is not implemented
> Somehow the notify seems to take up the `where' qualifier of the quer
In order to allow us to split easily across multiple machines, and move
things transparently, there following changes are being made:
AnonCVS
- to access the repository via anon-cvs, please connect to a
CVSROOT of:
:pserver:[EMAIL PROTECTED]:/projects/cvsroot
[redirect to -hackers]
Tom Lane writes:
> > The fact that the database server is wide-open in the default installation
> > is surely not good, but the problem is that we don't have a universally
> > accepted way to lock it down.
> > Another option would be to set the unix domain socket permissi
> > Sep 6 02:09:30 mx postgres[13468]: [9] FATAL 2:
> > XLogFlush: request(1494286336, 786458) is not satisfied --
> > flushed to (23, 2432317444)
First note that Denis could just restart with wal_debug = 1
to see bad request, without code change. (We should ask ppl
to set wal_debug ON in the
Vince, has this been addressed?
> On Wed, 1 Aug 2001, Bruce Momjian wrote:
>
> >
> > This appeared on the JDBC list. Do we need to address this?
>
> Where's Peter Mount? Isn't he the maintainer?
>
> Vince.
>
> >
> > > I actually consider the biggest problem the fact the the 'official'
> >
Doug McNaught <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
>> Upshot: a client holding an open transaction, plus another client trying
>> to do VACUUM, can clog up the database for everyone else.
> Thanks for the clarification. But the original poster's problem, that
> VAC
On Thursday 06 September 2001 20:49, Tom Lane wrote:
> Denis Perchine <[EMAIL PROTECTED]> writes:
> Okay. As a temporary recovery measure, I'd suggest reducing that
> particular elog from STOP to DEBUG level. That will let you start up
> and run the database. You'll need to look through you
You may be interested in
http://www.ietf.org/internet-drafts/draft-ietf-syslog-reliable-12.txt which
builds a reliable syslog protocol on top of BEEP. There are free
implementations of BEEP in C and Java at http://beepcore.org
- Original Message -
From: "Matthew Hagerty" <[EMAIL PROTECTE
At 08:54 PM 9/5/2001 -0700, Ian Lance Taylor wrote:
>Tom Lane <[EMAIL PROTECTED]> writes:
>
> > > And no, "use syslog" doesn't count.
> >
> > Why not?
>
>The standard implementations of syslog lose log entries under heavy
>load, because they rely on a daemon which reads from a named pipe with
>a l
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Aren't there log-rotation utilities out there already? (I seem to
>> recall mention that Apache has one, for instance.) Seems like this
>> is a wheel we shouldn't have to reinvent.
> I'm aware of the Apache rotatelogs utility, b
Denis Perchine <[EMAIL PROTECTED]> writes:
> Sep 6 02:09:30 mx postgres[13468]: [9] FATAL 2: XLogFlush: request(1494286336,
>786458) is not satisfied --
> flushed to (23, 2432317444)
Yeek. Looks like you have a page somewhere in the database with a bogus
LSN value (xlog pointer) ... and, mo
Thus spake Tom Lane
> Also, I kinda thought the long-range solution was to encourage everyone
> to migrate to syslog logging ...
>
> > And no, "use syslog" doesn't count.
>
> Why not?
Well, one "why not" might be that syslog is not a guaranteed delivery
logging system. It might be good enough
Tom Lane <[EMAIL PROTECTED]> writes:
> Doug McNaught <[EMAIL PROTECTED]> writes:
> > Hmmm--AFAIK, VACUUM is supposed to grab locks on the tables it
> > processes, which will block until all open transactions against that
> > table are finished. So either VACUUM or your transactions will have
> >
Peter Harvey wrote:
>
> Anyone know how inherited tables are shown on an ERD... both the table
> and the connector (if any)?
>
> What I am looking for is how to draw this in the diagram.
An old S-Designor does it so:
---(end of broadcast)---
TI
Christopher Kings-Lynne writes:
> What's the problem with using newsyslog or logrotate at the moment? (ie.
> use the system log rotator)
The postmaster will never close the output file, so you can rotate all you
want, the original file will never be abandoned.
--
Peter Eisentraut [EMAIL PRO
Tom Lane writes:
> Aren't there log-rotation utilities out there already? (I seem to
> recall mention that Apache has one, for instance.) Seems like this
> is a wheel we shouldn't have to reinvent.
I'm aware of the Apache rotatelogs utility, but I'm not completely
satisfied with it.
1. It tr
Anyone know how inherited tables are shown on an ERD... both the table
and the connector (if any)?
What I am looking for is how to draw this in the diagram.
Peter
--
+---
| Data Architect
| your data; how you want it
| http://www.codebydesign.com
+--
40 matches
Mail list logo
