The Hermit Hacker kirjutas R, 20.06.2003 kell 08:28:
> On Fri, 20 Jun 2003, Tom Lane wrote:
>
> > > On Fri, 20 Jun 2003, The Hermit Hacker wrote:
> > > Is there a strong reason why tsearch isn't in gborg?
> >
> > I think text search is a pretty important facility that should
> > eventually be part
I am running a Java
application on Linux which connects to the Postgresql on Linux using jdbcodbc
bridge.
But this is the
error I am getting :
sun.jdbc.odbc.JdbcOdbcDriverjava.lang.ClassNotFoundException:
sun.jdbc.odbc.JdbcOdbcDriver at 0x4028115f:
java.lang.Throwable.Throwable(java.la
- Original Message -
From: "Jeroen T. Vermeulen" <[EMAIL PROTECTED]>
> I ran into the same need (Bruce, we discussed this at FOSDEM in Brussels
> this February) for libpqxx. My code tries to compensate for the
> possibility that the backend connection is lost while waiting for a reply
>
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
> How much later? clog is not kept forever.
Due to my setup, I could assure, that for the XID I ask for always
(ShmemVariableCache->nextXid - XID) < C (and C is in my case something
around 150).
holds. A possible solution co
On Fri, Jun 20, 2003 at 09:35:08AM +0200, Christian Plattner wrote:
>
> I see a race condition in this approach: if you reconnect too fast, and the
> backend which actually should commit is still in progress (assume it takes a
> while to commit for whatever reasons) you get the impression that it
- Original Message -
From: "Jeroen T. Vermeulen" <[EMAIL PROTECTED]>
> > I see a race condition in this approach: if you reconnect too fast, and
the
> > backend which actually should commit is still in progress (assume it
takes a
> > while to commit for whatever reasons) you get the impr
On Thu, 19 Jun 2003, The Hermit Hacker wrote:
> On Thu, 19 Jun 2003, Andrew Dunstan wrote:
>
> >
> > Maybe a better strategy would be to get a release out soon but not wait
> > 6 months for another release which would contain the Win32 port and the
> > PITR stuff (assuming those aren't done in t
On Fri, 20 Jun 2003, Christopher Kings-Lynne wrote:
> > Why part of the core distribution, and not just left as a loadable module,
> > like it is now?
>
> The day I can go 'CREATE FULLTEXT INDEX ...' just like MySQL can I will be a
> very happy chappy...
>
with new tserach v2 we're pretty close t
I am running an agent in the domino server that
connects to a database in Postgresql through odbc dsn.I am getting an error
"Error Creating product object" at the line Set con = New
ODBCConnectionHere is the code :Option PublicUselsx
"*LSXODBC"Sub Initialize Dim con As
ODBCConnection
The Hermit Hacker wrote:
On Thu, 19 Jun 2003, Andrew Dunstan wrote:
Maybe a better strategy would be to get a release out soon but not wait
6 months for another release which would contain the Win32 port and the
PITR stuff (assuming those aren't done in time for this release).
Just a thought.
When you change the owner of a table and relacl is null, then the new
owner obtains all privileges, because the default privileges apply to the
current owner. But when relacl is not null, the old owner retains all
privileges and the new owner has none.
Perhaps the privileges of the owner should b
On Fri, Jun 20, 2003 at 10:20:14AM +0200, Christian Plattner wrote:
>
> Well, I wouldn't rely solely on TCP when assuring consistency. Also, I don't
> think that the backend will ever inspect its TCP socket while committing.
No, but its underlying IP stack would.
> btw: There could be also oth
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
> How much later? clog is not kept forever.
I took a deeper look into the source. Forget my last posting.
As far as I understand your code there is only one chance that information
in clog gets lost:
If XIDs are reused then Exte
- Original Message -
From: "Jeroen T. Vermeulen" <[EMAIL PROTECTED]>
> > btw: There could be also other reasons for the client to loose the
> > connection (i.e. client process crashes).
>
> In that case the client would lose all its state as well, so not really
> a problem that can be ha
On Fri, Jun 20, 2003 at 02:41:29PM +0200, Christian Plattner wrote:
>
> Well, my client (actually it is a middleware layer which routes transactions
> to a set of replicas) keeps its own log, because it must be able to handle
> arbitary failures. So it never looses its state.
In that case perhaps
On Thu, 2003-06-19 at 21:22, Christopher Kings-Lynne wrote:
> > There is no alternative, unless you want the command to be
> > non-roll-back-able.
>
> Well, you can do a cluster-type table duplication...
Thats still double the disk space, although that has the nice side
effect of not requiring a
"Christian Plattner" <[EMAIL PROTECTED]> writes:
> From: "Tom Lane" <[EMAIL PROTECTED]>
>> How much later? clog is not kept forever.
> ... Ofcourse one should not do a
> VACUUM FULL while not being sure about the status of a transaction in the
> past :)
As long as you haven't done a cluster-wide
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Perhaps the privileges of the owner should be represented with a different
> flag in the aclitem, alongside world, group, public?
Seems reasonable to me. It always struck me as kind of odd that the
owner's name would become explicit in the ACL as soo
"Christian Plattner" <[EMAIL PROTECTED]> writes:
> From: "Tom Lane" <[EMAIL PROTECTED]>
>> How much later? clog is not kept forever.
> As far as I understand your code there is only one chance that information
> in clog gets lost:
> If XIDs are reused then ExtendCLOG will overwrite existing entri
On Fri, 2003-06-20 at 04:41, Nigel J. Andrews wrote:
>
> On Thu, 19 Jun 2003, The Hermit Hacker wrote:
>
> > On Thu, 19 Jun 2003, Andrew Dunstan wrote:
> >
> > >
> > > Maybe a better strategy would be to get a release out soon but not wait
> > > 6 months for another release which would contain t
On Fri, 2003-06-20 at 06:59, Justin Clift wrote:
> The Hermit Hacker wrote:
> > On Thu, 19 Jun 2003, Andrew Dunstan wrote:
> Yep, this makes sense. Looks like it'll be PostgreSQL 7.4 being all the
> present improvements, but without PITR and Win32. Then, in a few months
> (hopefully less than 3
Robert Treat <[EMAIL PROTECTED]> writes:
> On Fri, 2003-06-20 at 06:59, Justin Clift wrote:
>> The only thing that makes me wince is that we have a protocol change at
>> PostgreSQL 7.4 release instead of 8.0.
> ...which is why I'd advocate making this release an 8.0 regardless of
> win32 or pitr.
And, actually, for some reason I hadn't thought of the tsearch as being
another 'INDEX' type ... I crawl back over and be quiet now :)
Oleg, as far as commits are concerned, I have no problems with extending
the privileges to one of your guys for this, just email me seperately who,
and I'll get i
On Fri, 2003-06-20 at 10:42, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > On Fri, 2003-06-20 at 06:59, Justin Clift wrote:
> >> The only thing that makes me wince is that we have a protocol change at
> >> PostgreSQL 7.4 release instead of 8.0.
>
> > ...which is why I'd advocate
Robert,
> Well, I suppose that history has shown that waiting on specific features
> causes trouble with postgresql development, but I don't see why a
> release can't be based around waiting for feature x as long as feature x
> is being actively worked on by trusted developers who have an endgame
Robert Treat <[EMAIL PROTECTED]> writes:
> On Fri, 2003-06-20 at 10:42, Tom Lane wrote:
>> ... The backend will still talk to old clients, and libpq will
>> still talk to old backends, so I don't think the protocol change is
>> really going to cause a flag day for anyone. On a technical level it'
On Fri, 2003-06-20 at 11:21, Josh Berkus wrote:
> Robert,
>
> > Well, I suppose that history has shown that waiting on specific features
> > causes trouble with postgresql development, but I don't see why a
> > release can't be based around waiting for feature x as long as feature x
> > is being a
The attached patches against 7.3 and 7.4 fix a subtraction carry bug in
xlog.c.
--
John Nield
[EMAIL PROTECTED]
Index: pgsql-server-7_3/src/backend/access/transam/xlog.c
diff -c pgsql-server-7_3/src/backend/access/transam/xlog.c:1.1.1.1
pgsql-server-7_3/src/backend/access/transam/xlog.c:1.1.1.1.
"J.R. Nield" <[EMAIL PROTECTED]> writes:
> The attached patches against 7.3 and 7.4 fix a subtraction carry bug in
> xlog.c.
This is simply a waste of cycles, because xrecoff can never be zero
(if it were, it'd be pointing at a page header, which is not a valid
record location). If you look aroun
My understanding of "schema" that I discovered
in 7.3 (I don't think they were available before)
is that you can have two tables with the same name
if they are in different schemas.
I have done a google search, as well as archive search
but
pg_dump and pg_dumpall are broken if a database
contains
Robert,
> absolutely not. this is a x style of development vs. y style of
> development discussion. many many projects, commercial and open source,
> use a style of releasing based on features included in a given version.
> In fact I'd be willing to say that the majority of open source projects
>
Josh Berkus <[EMAIL PROTECTED]> writes:
> So looked at from that perspective, our mistake was to try to cram too many
> features into 7.4 ... more than could possibly get done in 6-8 months.
It's more that we thought that all these features would get done in
about the same timeframe, and (not
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> On Thu, 19 Jun 2003, Robert Treat wrote:
>
>> Well, I suppose that history has shown that waiting on specific features
>> causes trouble with postgresql development, but I don't see why a
>> release can't be based around waiting for feature x as long
We only have sporadic support to rename objects, change the owner of
objects, and no support to change the schema of an object. So how about a
big bang to add support for these three operations for every object where
it is applicable? I hope to do it without a separate parse structure and
routine
On Thu, 2003-06-19 at 12:09, Jon Jensen wrote:
> On Thu, 19 Jun 2003, Christopher Kings-Lynne wrote:
>
> > Does anyone care about contrib/reindexdb anymore?
>
> I would've found it handy, but didn't know about it and wrote my own in
> Perl. Inside a transaction it drops the index then rebuilds it
> -Original Message-
> From: Jason Earl [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 20, 2003 10:45 AM
> To: The Hermit Hacker
> Cc: Robert Treat; Tom Lane; Christopher Kings-Lynne; Bruce
> Momjian; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> The
what i was trying to do was maintain an array of Buffer pool clusters.
What i did previously was change the pointers around in the freelist so
instead of one i have 4. Now each buffer pool is called a BP cluster.
Within this BP cluster i have things like cluster id, freelist descriptor
etc, and a l
Nailah Ogeer <[EMAIL PROTECTED]> writes:
> So what is happening is that i enter the relation ids into the BP cluster
> linked list fine and every time i call psql, it automatically deletes.
Sounds to me like you are trying to keep stuff in backend-local memory
that needs to be in shared memory.
Well here's the thing. Before i was trying to use ShmemInitStruct in
buf_init.c. The problem with this is that you can't shrink or grow shared
memory. That is why i switched over and just used malloc. So i seem to be
in a big dilemma, on one hand, if i use malloc, i can't keep this info i
need; and
> "Nailah" == Nailah Ogeer <[EMAIL PROTECTED]> writes:
Nailah> Well here's the thing. Before i was trying to use
Nailah> ShmemInitStruct in buf_init.c. The problem with this is
Nailah> that you can't shrink or grow shared memory. That is why i
Nailah> switched over and just use
On Wed, Jun 18, 2003 at 10:01:37AM +1000, Gavin Sherry wrote:
> On Tue, 17 Jun 2003, Tom Lane wrote:
>
> > "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > > The reason I mention it is that Postgres already supports O_DIRECT I think
> > > on some other platforms (for whatever reason).
> >
Dann Corbit wrote:
> > -Original Message-
> > From: Jason Earl [mailto:[EMAIL PROTECTED]
> > Sent: Friday, June 20, 2003 10:45 AM
> > To: The Hermit Hacker
> > Cc: Robert Treat; Tom Lane; Christopher Kings-Lynne; Bruce
> > Momjian; PostgreSQL-development
> > Subject: Re: [HACKERS] Two wee
"Dann Corbit" <[EMAIL PROTECTED]> writes:
>>
>> Why couldn't you just release the win32 version of 7.4 when
>> it was finished. If it takes an extra month then that just
>> gives you guys the chance to circulate *two* press releases.
>> The Native Win32 port is likely to make a big enough spl
> -Original Message-
> From: Jason Earl [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 20, 2003 3:32 PM
> To: Dann Corbit
> Cc: Jason Earl; The Hermit Hacker; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> "Dann Corbit" <[EMAIL PROTECTED]> writes:
> >>
On Fri, Jun 20, 2003 at 03:39:47PM -0700, Dann Corbit wrote:
> We (at CONNX Solutions Inc.) have a formal release procedure that
> includes many tens of thousands of automated tests using dozens of
> different platforms. [...]
>
> If there is no procedure for PostgreSQL of this nature, then ther
"Dann Corbit" <[EMAIL PROTECTED]> writes:
>> -Original Message-
>> From: Jason Earl [mailto:[EMAIL PROTECTED]
>> Sent: Friday, June 20, 2003 3:32 PM
>> To: Dann Corbit
>> Cc: Jason Earl; The Hermit Hacker; PostgreSQL-development
>> Subject: Re: [HACKERS] Two weeks to feature freeze
>>
>>
On Thu, Jun 19, 2003 at 23:01:19 +0200,
Kurt Roeckx <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 17, 2003 at 11:01:27PM -0500, Bruno Wolff III wrote:
> >
> > My system does have its own sockaddr_storage definition. I think
> > it uses __ss_ as the prefix. Also, after looking at the fallback
> > defi
On Fri, Jun 20, 2003 at 18:56:30 -0500,
Bruno Wolff III <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 19, 2003 at 23:01:19 +0200,
> Kurt Roeckx <[EMAIL PROTECTED]> wrote:
> > On Tue, Jun 17, 2003 at 11:01:27PM -0500, Bruno Wolff III wrote:
> > >
> > > My system does have its own sockaddr_storage de
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Are there any tricky problems with any of these operations?
A few. Moving a table across schemas would require moving its indexes
and rowtype as well; conversely you should forbid moving the indexes and
rowtype by themselves, or altering their owners
> -Original Message-
> From: Jason Earl [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 20, 2003 4:43 PM
> To: Dann Corbit
> Cc: Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> "Dann Corbit" <[EMAIL PROTECTED]> writes:
>
> >> -Original Me
This change (I'm sure this will wrap poorly -- sorry):
http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/include/libpq/pqcomm.h.diff?r1=1.85&r2=1.86
modified SockAddr, but no corresponding change was made here
(fe-auth.c:612):
case AUTH_REQ_KRB5:
#ifdef KRB5
if (pg_krb5_sendauth(PQe
Jason Earl <[EMAIL PROTECTED]> writes:
> The fact of the matter is that the Win32 specific bits are the parts
> that are likely to break in the new port.
Actually, what scares me about this is the probability that the Win32
port will break other platforms. The changes look to be invasive enough
t
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> If there is no procedure for PostgreSQL of this nature, then there
> really needs to be.
Are you volunteering to create it? Step right up.
> I am sure that MySQL must have something in place
> like that. Their "Crash-Me" test suite shows (at least) th
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> It would be nice to have a system which could receive a patch and
> compile and verify that it passes the tests before it goes to Bruce's
> queue; or compile on multiple platforms to check for portability
> problems, for example.
It happens not infreque
Jason Earl <[EMAIL PROTECTED]> writes:
> Hmm... I must have missed the huge corporation paying for in house
> testing of PostgreSQL. In the Free Software world the "beta team" is
> all of those people that need the new features so badly that they are
> willing to risk their own data and hardware t
Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
It would be nice to have a system which could receive a patch and
compile and verify that it passes the tests before it goes to Bruce's
queue; or compile on multiple platforms to check for portability
problems, for example.
*snip*
Anot
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 20, 2003 8:36 PM
> To: Dann Corbit
> Cc: Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> "Dann Corbit" <[EMAIL PROTECTED]> writes:
> > If there is no proced
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 20, 2003 8:58 PM
> To: Jason Earl
> Cc: Dann Corbit; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> Jason Earl <[EMAIL PROTECTED]> writes:
> > Hmm... I must have misse
--- Dann Corbit <[EMAIL PROTECTED]> wrote:
> Why couldn't you just release the win32 version of 7.4
> when it was finished.
I agree. Don't delay *nix release because of win32 port is not ready. To many
users win32 port is of marginal importance anyway.
__
Do
Thomas Swan <[EMAIL PROTECTED]> writes:
> Have you considered something similar to the Mozilla tinderbox approach
> where you have a daemon checkout the cvs, compile, run regression tests,
> and report a status or be able to report a status?
Tinderbox is pretty cool. Who wants to set it up?
"Dann Corbit" <[EMAIL PROTECTED]> writes:
>> ...ROTFL... Crash-Me is not a regression test. It is a
>> marketing effort.
> Their marketing effort checks for STANDARDS conformance against over
> several hundred distinct, important properties.
If you'd not spelled STANDARDS in caps I'd not have
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 20, 2003 9:19 PM
> To: Dann Corbit
> Cc: Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> "Dann Corbit" <[EMAIL PROTECTED]> writes:
> >> ...ROTFL... Crash-M
On Fri, Jun 20, 2003 at 09:25:08PM -0700, Dann Corbit wrote:
Citing Tom Lane:
> > I have been through crash-me in some detail, and it left a
> > very bad taste in my mouth. Don't bother holding it up as an
> > example of good practice.
>
> Every single test in their list is interesting and use
> Thats still double the disk space, although that has the nice side
> effect of not requiring a vacuum.
Also, a rollback after 99% of the updates have been done will waste no
diskspace...
Chris
---(end of broadcast)---
TIP 4: Don't 'kill -9' the
> -Original Message-
> From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 20, 2003 10:00 PM
> To: Dann Corbit
> Cc: Tom Lane; Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> On Fri, Jun 20, 2003 at 09:25:08PM -0700, Dann Corb
> The command is: ALTER THING name AUTHORIZATION username; (This is
> consistent with the CREATE SCHEMA syntax. Anyone like OWNER better?)
k
WHy not copy the exiting ALTER TABLE / OWNER TO syntax?
Chris
---(end of broadcast)---
TIP 8: explain an
> We (at CONNX Solutions Inc.) have a formal release procedure that
> includes many tens of thousands of automated tests using dozens of
> different platforms. There are literally dozens of machines (I would
> guess 70 or so total) running around the clock for 7 days before we even
> know if we ha
> -Original Message-
> From: Christopher Kings-Lynne [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 20, 2003 10:14 PM
> To: Dann Corbit
> Cc: Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> > We (at CONNX Solutions Inc.) have a formal release
> I don't have a lot of faith in huge automated test efforts. They're
> great at ensuring you don't make the same mistakes you made once before,
> but in my experience the nastiest bugs are the ones you haven't seen
> before and would never in a million years have dreamed to test for.
> Thus, the
> Things like that drive the credibility of the whole thing to the floor.
> Maybe something like this should exist for Postgres, but it's not
> crash-me. Maybe the NIST compliance test is adequate.
Plus I belive the RedHat people are getting PostgreSQL through the NIST
compliance tests at the mom
> Sounds like testing for the existence of a bug.
> X = NULL
> X <= NULL
> X >= NULL
> Etc. must always test false, regardless of the contents of X. Test for
> equality with NULL is a conformance error if NULL == NULL returns true.
They should all return NULL, not false...
> > dates like '00-00-
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> Maybe the NIST compliance test is adequate.
> Plus I belive the RedHat people are getting PostgreSQL through the NIST
> compliance tests at the moment...I'd love to see MySQL pass them...
FWIW, the first pass of those tests is complete, and i
> If you mean the one that comes with PostgreSQL, then I think the MySQL
> test is better. The PostgreSQL test seems to focus more on extensions
> than anything else.
What the? It tests no extensions. The extensions have their own
regression tests.
> Most of the criticism leveled at their effo
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> Look at this:
> http://www.mysql.com/information/crash-me.php?mysql_4_1=on&postgres=on
This looks a little cleaner than the last time I looked at it (more than
three years ago), but it's still fundamentally a marketing effort. It
is not an exercise in s
74 matches
Mail list logo
