On Thu, 10 Jul 2003 01:33 pm, Christopher Kings-Lynne wrote:
> FreeBSD alpha.cacheboy.net 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Feb 3
Hmm... I have 7.4devel built on FreeBSD 4.8 Intel running ipv6 at home - I'll
try the same tonight. It might help determine if it's architecture or OS.
Regards,
Hello To Everyone,
iam testing postgresql 7.2.1 in my linix envoriment.postgres is security builder. its
very stonger then other database management tools. any thing hols on security issues
of postgres. pl any thing on security pl mail me
subbiah.k.j
System Administrator
Indus Software
A b
Colin Ng (IWE) wrote:
> Hi everybody,
>
> I created a db with encoding 'SQL-ASCII'. And I wrote a JSP application
> to manipulate corporate information which including both
> Traditional/Simplified Chinese characters. However, I can read both
> Traditional/Simplified Chinese information from m
From: Kurt Roeckx <[EMAIL PROTECTED]>
Subject: Re: [HACKERS] PostgreSQL 7.4devel - LOG: PGSTAT: socket() failed: Invalid
argument
Date: Sun, 6 Jul 2003 18:44:35 +0200
;;; On Sun, Jul 06, 2003 at 06:30:04PM +0200, Kurt Roeckx wrote:
;;; > Try the attached patch instead.
;;;
;;; Oops, that one was
> Interesting... I'm running OSF on Alpha and I get the usual
> "/tmp/.s.PGSQL.5432". Perhaps it's related to IPv6 socket changes? I'm
pretty
> sure we don't have IPv6 support, so it would make sense it doesn't show up
> here if I guess right.
>
> What's your `uname -a`? FreeBSD has had IPv6 suppor
On Thu, 10 Jul 2003 12:35 pm, Christopher Kings-Lynne wrote:
> When I run psql on freebsd/alpha with latest CVS and no postmaster running,
> I get this:
> bizarre socket name
Interesting... I'm running OSF on Alpha and I get the usual
"/tmp/.s.PGSQL.5432". Perhaps it's related to IPv6 socket chan
On Thu, 10 Jul 2003, Christopher Kings-Lynne wrote:
> > Hmm... I was thinking the index could be somehow corrupted. However,
> > it's strange that all databases have the same problem, since pg_trigger
> > is not shared across databases.
> >
> > Have you tried reindexing pg_trigger?
>
> Can't -
Hi Guys,
Is there a new function I can use in 7.4 to get an array as a recordset?
eg. I want an easy way of splitting up all the aclitems from an aclitem[],
rather than trying to parse it all in PHP. (usernames with commas in them
are the problem you see!)
Chris
---(end
"scott.marlowe" <[EMAIL PROTECTED]> writes:
> On Wed, 9 Jul 2003 [EMAIL PROTECTED] wrote:
>> Wrong again. Oracle also capitalizes the first letter after a comma,
>> semicolon, colon, period, and both a single and double quote. (And that's
>> all I've tested so far.)
> It sounds like Oracle is
When I run psql on freebsd/alpha with latest CVS and no postmaster running,
I get this:
bash-2.03$ psql test
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "ùÿÿÿØ`"?
What's with the biz
How's this for an idea? We release a statically compiled version of pg_dump
(from the 7.4 tree say) that is able to dump 7.3, 7.2 databases etc. We
recommend to people that they use that to dump their existing database?
We could have it continually available as a database dumper...
Chris
> Hmm... I was thinking the index could be somehow corrupted. However,
> it's strange that all databases have the same problem, since pg_trigger
> is not shared across databases.
>
> Have you tried reindexing pg_trigger?
Can't - I can't log into any database.
Maybe it's one of psql's startup q
On Thu, Jul 10, 2003 at 11:45:09AM +1000, Gavin Sherry wrote:
> On Thu, 10 Jul 2003, Christopher Kings-Lynne wrote:
>
> > Just saw this on our demo server:
> >
> > [EMAIL PROTECTED]:~/htdocs/webdb/conf# /usr/local/pgsql-7.3.3/bin/psql -p5473
> > phppgadmin
> > psql: FATAL: cannot open segment 1
On Thu, 10 Jul 2003, Christopher Kings-Lynne wrote:
> Just saw this on our demo server:
>
> [EMAIL PROTECTED]:~/htdocs/webdb/conf# /usr/local/pgsql-7.3.3/bin/psql -p5473
> phppgadmin
> psql: FATAL: cannot open segment 1 of relation
> pg_trigger_tgrelid_tgname_index (target block 8310112): No suc
> "Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> > Let's start beta July 18 or that weekend. I can catch up with email by
> > then, and Tom will have the elog() changes done by then too.
>
> What about the PITR ( point in time recovery )?
> I mean: the 7.4 will have PITR or not ?
Nope.
Chris
-
"Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> Let's start beta July 18 or that weekend. I can catch up with email by
> then, and Tom will have the elog() changes done by then too.
What about the PITR ( point in time recovery )?
I mean: the 7.4 will have PITR or not ?
Thank you in advance
Gaetan
OK. Roger.
---
The Hermit Hacker wrote:
> On Wed, 9 Jul 2003, Bruce Momjian wrote:
>
> >
> > Let's start beta July 18 or that weekend. I can catch up with email by
> > then, and Tom will have the elog() changes done by th
Just saw this on our demo server:
[EMAIL PROTECTED]:~/htdocs/webdb/conf# /usr/local/pgsql-7.3.3/bin/psql -p5473
phppgadmin
psql: FATAL: cannot open segment 1 of relation
pg_trigger_tgrelid_tgname_index (target block 8310112): No such file or
directory
Any solution? Happens on all databases.
Ch
On Wed, 9 Jul 2003, Bruce Momjian wrote:
>
> Let's start beta July 18 or that weekend. I can catch up with email by
> then, and Tom will have the elog() changes done by then too.
Let's make it July 21st then ... I'm with family next week in the middle
of nowhere in a tent ... not even sure if I'
On Tue, Jul 08, 2003 at 07:41:48AM -0700, Jenny - wrote:
> [unquotable HTML, please post only text/plain!]
At transaction start
(src/backend/access/transam/xact.c::StartTransaction()),
src/backend/storage/lmgr/lmgr.c::XactLockTableInsert() is executed,
which takes a special lock on a ficticious X
Let's start beta July 18 or that weekend. I can catch up with email by
then, and Tom will have the elog() changes done by then too.
---
Bruce Momjian wrote:
> You might have noticed I am behind on email.
>
> I had a big fa
On Wed, 9 Jul 2003 [EMAIL PROTECTED] wrote:
> > As far as I can tell, not capitalizing the first letter after a dash
> > is the only inconsistency with Oracle's implementation of this function.
>
> Wrong again. Oracle also capitalizes the first letter after a comma,
> semicolon, colon, period,
> As far as I can tell, not capitalizing the first letter after a dash
> is the only inconsistency with Oracle's implementation of this function.
Wrong again. Oracle also capitalizes the first letter after a comma,
semicolon, colon, period, and both a single and double quote. (And that's
all I
>
> The initcap function is not completely consistent with Oracle's initcap
> function:
>
> SELECT initcap('alex hyde-whyte');
>
> In Oracle 9.2i this will return 'Alex Hyde-White', in PostgreSQL 7.3.3
> it returns 'Alex Hyde-white'.
No, it doesn't change the 'y' to an 'i', that's a typo i
The initcap function is not completely consistent with Oracle's initcap
function:
SELECT initcap('alex hyde-whyte');
In Oracle 9.2i this will return 'Alex Hyde-White', in PostgreSQL 7.3.3
it returns 'Alex Hyde-white'.
It looks like a relatively simple change to oracle_compat.c in
backend/ut
Hello:
You do need to use Sync rather than Flush to create transaction
boundaries and error restart points. I suspect your problem was coming
from having only a Flush and not a Sync between the CREATE DATABASE and
the *prior* command.
Huummm there are no prior executed commands, the CREATE DATA
You might have noticed I am behind on email.
I had a big family reunion at my house during the July 4th holiday, with
16 people staying for 2-4 days. This cut into my email time, and I left
for OSCON and Linuxtag right after that.
I am stuggling to read email and be visible at OSCON. I am not s
Carlos Guzman Alvarez <[EMAIL PROTECTED]> writes:
> Hello:
>>> No, it should just work. Can you give a test case? Do you see similar
>>> problems with other utility commands, or is it only CREATE DATABASE?
> I have made a litlle test more and i have it working now, i have made
> change for send
On Tue, 2003-07-08 at 21:31, ivan wrote:
> What do you think about :
>
> 1. OPTION RETURNS NULL ON NULL INPUT (when function is created) change to
> RETURNS ON NULL INPUT ???
I personally think this should be up to the specific function to
capture. This way it could be a complex result.
Hello:
I continue to work in the implementation of the 3.0 protocol in C#, i'm
making a test that consist on:
- Create a database.
- Create a table in the new database.
- Start transaction.
- Insert 100 rows of data in the new table.
- Commit transaction.
For start a transaction i send a Query m
Hello:
> No, it should just work. Can you give a test case? Do you see similar
> problems with other utility commands, or is it only CREATE DATABASE?
I have made a litlle test more and i have it working now, i have made
change for send a Sync message instead of a Flush message after execute
th
Hello,
> On Mon, Jul 07, 2003 at 12:55:06AM +0900, [EMAIL PROTECTED] wrote:
> >
> > When hints.ai_family is PF_UNSPEC, getaddrinfo() returns two entries,
> > first one being IPv6 one, and the second one is IPv4 one, even if
> > IPv6 support is not compiled in the kernel(this is true at least on
>
32 matches
Mail list logo
