I have backed out the changes to ODBC that removed compatibility with
<6.4 servers, so the 7.1 ODBC code still supports the older servers.
I have changed the dialog box from "6.4+" to "7.X,6.4+" to make it less
confusing for users.
Is that ODBC protocol dialog box needed? Can the client auto-det
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> Also, could the "-F" option be disabled now that WAL is enabled? Or is
> there still some reason to encourage/allow folks to use it?
I was the one who put it back in after Vadim turned it off ;-) ... and
I'll object to any attempt to remove the option
> Since there is a fundamental recovery problem if the WAL file
> disappears, then perhaps we should have a workaround which can ignore
> the requirement for that file on startup? Or maybe we do already?
> Vadim??
>
> Also, could the "-F" option be disabled now that WAL is enabled? Or is
> there
> Guilty as charged I am afraind... :( Here, I though with WAL and
> all (bad pun :), I would not need fsync anymore and decided to be
> reckless. Guess I ought to reconsider that decision Though wasn't WAL
> supposed to remove the need for fsync, or was it just to improve recovery
> a
On Tue, 13 Feb 2001, Mikheev, Vadim wrote:
> > Might it be, that pg_control is older than it should be ?
> > I mean, that the write to pg_control did not make it to disk,
> > but the checkpoint already completed (removed the logs) ?
>
> Well, WAL does *pg_fsync()* of pg_control before removing o
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> Are we not allowed to use NEW and OLD in an EXECUTEd statement?
Not for 7.1, I'm afraid. EXECUTE doesn't provide *any* connection
to the plpgsql function's local namespace; it just hands off the
constructed string to the main SQL parser.
In most cases
Lamar Owen writes:
> > I don't think so. On RH 6.1, strncmp() is the same it's ever been:
> [snip]
>
> Is that the code after any glibc RPM patches are applied?
Yes.
> I base my assertion on running test queries on a RedHat 6.1 box over a
> year ago, using the non-locale 6.5.3 RPMset I distrib
Peter Eisentraut wrote:
> Lamar Owen writes:
> > And building without locale support doesn't work, either, because, at
> > least on RH 6.1, strncmp() is buggered to use the locale's collation.
> I don't think so. On RH 6.1, strncmp() is the same it's ever been:
[snip]
Is that the code after any
IIRC, trigger functions don't take parameters, they're
func() returns opaque. The arguments given in create trigger
are passed in a different way. That's why the error message
is saying dbuser_account() is missing.
On Tue, 13 Feb 2001, Rod Taylor wrote:
> Sorry, Postgres 7.1 beta4
> --
> Ro
Lamar Owen writes:
> And building without locale support doesn't work, either, because, at
> least on RH 6.1, strncmp() is buggered to use the locale's collation.
I don't think so. On RH 6.1, strncmp() is the same it's ever been:
int
strncmp (s1, s2, n)
const char *s1;
const char *s2
Are we not allowed to use NEW and OLD in an EXECUTEd statement?
Postgresql 7.1 beta 4
Received:
ERROR: NEW used in non-rule query
from within a plpgsql function (using an EXECUTE statement of course).
That aside, is there anyway to do:
v_var := NEW.v_variable;
As it would be an acceptable a
> Might it be, that pg_control is older than it should be ?
> I mean, that the write to pg_control did not make it to disk,
> but the checkpoint already completed (removed the logs) ?
Well, WAL does *pg_fsync()* of pg_control before removing old
logs, so it's only possible if Ryan run PG with -F
The 7.1 PostgreSQL ODBC client interface will no longer be able to talk
to PostgreSQL servers earlier than 6.4. The backward compatibility code
has been removed.
Does anyone want such compatibility?
(FYI, libpq and all interfaces based on it can't talk to such servers
either.)
--
Bruce Mom
I have updated the developers globe web page and have added a new
section entitled "Other Contributors".
I generated the "Other Developers" section by pulling names from
all versions of the TODO list. Of course, this doesn't list _all_
contributors, but just the larger ones. I am glad to add mo
Tom Lane wrote:
> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > I know this is not PostgreSQL's fault but the broken locale data on
> > certain platforms. The problem makes it impossible to use PostgreSQL
> > RPMs in Japan.
> > I'm looking for solutions/workarounds for this problem.
> >> Build a s
Sorry, Postgres 7.1 beta4
--
Rod Taylor
There are always four sides to every story: your side, their side, the
truth, and what really happened.
- Original Message -
From: "Rod Taylor" <[EMAIL PROTECTED]>
To: "Hackers List" <[EMAIL PROTECTED]>
Sent: Tuesday, February 13, 2001 10:35 AM
Subj
Create function, attempt to create trigger fails, yet function
obviously exists. I can't seem to typecast the trigger parameters.
\df even misses the function.
temp=# CREATE FUNCTION dbuser_account(varchar(40), varchar(40),
varchar(40))
temp-# RETURNS OPAQUE
temp-# AS
'/usr/home/rbt/temp/pos
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> I know this is not PostgreSQL's fault but the broken locale data on
> certain platforms. The problem makes it impossible to use PostgreSQL
> RPMs in Japan.
>>
> I'm looking for solutions/workarounds for this problem.
>>
>> Build a set of RPMs without lo
On Tue, 13 Feb 2001, Vadim Mikheev wrote:
> I don't remember why there is abort() in XLogFileOpen just before
> appropriate elog(STOP) there - I'll remove it in few moments, - but
> it's already obvious why open failed: there is no file with checkpoint
> record pointed by pg_control - data/pg_xlo
> >Thanks, I checked it. So if I want my own output, I must set CONV_ALL=1,
> >right?
>
> No. pg_dump now does what you want by default. If not, let me know...
OK, thanks, this behaviour is excellent for me... :-)
--
Kov\'acs, Zolt\'an
[EMAIL PR
At 13:35 13/02/01 +0100, Kovacs Zoltan wrote:
>> I have modified formatLiteralString to accept an arg that tells it how to
>> handle LF & TAB. Now, it will encode *everything* except in comments and
>> procedure bodies.
>Thanks, I checked it. So if I want my own output, I must set CONV_ALL=1,
>rig
> I have modified formatLiteralString to accept an arg that tells it how to
> handle LF & TAB. Now, it will encode *everything* except in comments and
> procedure bodies.
Thanks, I checked it. So if I want my own output, I must set CONV_ALL=1,
right?
Zoltan
--
Kov\'acs, Z
Nathan Myers wrote:
>
> On Mon, Feb 12, 2001 at 09:59:37PM -0500, Tom Lane wrote:
> > Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > > I know this is not PostgreSQL's fault but the broken locale data on
> > > certain platforms. The problem makes it impossible to use PostgreSQL
> > > RPMs in Japan.
> > > #2 0x20dc71 in abort () from /lib/libc.so.6
> > > #3 0x8080495 in XLogFileOpen ()
> >
> > Hm. Evidently it's failing to open the xlog file, but the code is set
> > up in such a way that it dies before telling you why :-( Take a look
> > at XLogFileOpen in src/backend/access/transam/xlog
> > #2 0x20dc71 in abort () from /lib/libc.so.6
> > #3 0x8080495 in XLogFileOpen ()
>
> Hm. Evidently it's failing to open the xlog file, but the code is set
> up in such a way that it dies before telling you why :-( Take a look
> at XLogFileOpen in src/backend/access/transam/xlog.c and tweak
25 matches
Mail list logo
