Are any PostgreSQL hackers planning to be at Linuxtag in Karlsruhe?
-- ams
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
"Victor Y. Yegorov" <[EMAIL PROTECTED]> writes:
> * Alvaro Herrera <[EMAIL PROTECTED]> [08.06.2005 00:39]:
>> Huh, why? You need to grab the relation extension block
>> (LockRelationForExtension in CVS tip).
> Really? Didn't knew that.
> Consider:
> 1) I add 2 pages to the newly-created relatio
Andrew - Supernews <[EMAIL PROTECTED]> writes:
> On 2005-06-07, "Alexander M. Pravking" <[EMAIL PROTECTED]> wrote:
>> A week ago, I had a discussion with AndrewSN (Andrew Sullivan, I
>> suppose)
> No, that was me.
I know who Andrew Sullivan is, but who are *you* exactly?
(Not to be too rude, but
On 2005-06-07, "Alexander M. Pravking" <[EMAIL PROTECTED]> wrote:
> A week ago, I had a discussion with AndrewSN (Andrew Sullivan, I
> suppose)
No, that was me.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)--
On Tue, Jun 07, 2005 at 05:48:31PM -0400, Tom Lane wrote:
> Comments? Anyone else ever wished they had this?
Hmm. There's another problem which shows up when the server throws an
error about an invalid allocation request. This also happens when a
varlena field is corrupted, but you don't have
A week ago, I had a discussion with AndrewSN (Andrew Sullivan, I
suppose) on #postgresql IRC channel about the following issue.
I have a function, ss_info(text, text) which stores/replaces given key
and value in ss_info temporary table; the table is created unless exists
yet. The function looked l
On Mon, 2005-06-06 at 22:09 -0400, Bruce Momjian wrote:
> After months of being behind, I have gone through my entire mailbox and
> addressed all the patches held over from 8.0beta. I have loaded up the
> patch queue and will apply them in a day or two.
>
> http://momjian.postgresql.org/cgi
* Alvaro Herrera <[EMAIL PROTECTED]> [08.06.2005 00:39]:
> Huh, why? You need to grab the relation extension block
> (LockRelationForExtension in CVS tip).
Really? Didn't knew that.
Consider:
1) I add 2 pages to the newly-created relation
using P_NEW as BlockNumber;
2) then I do LockRelation
I was just helping out some Red Hat colleagues who were trying to deal
with a corrupted database in which pg_dump was failing like so:
pg_dump: Error message from server: ERROR: missing chunk number 3 for toast
value 205026
Frequently the best recovery action for this involves finding and
delet
On Tue, Jun 07, 2005 at 07:52:57PM +0300, Victor Y. Yegorov wrote:
> * Tom Lane <[EMAIL PROTECTED]> [07.06.2005 07:59]:
> > Why bother? Just write each page when you need to --- there's no law
> > that says you must use P_NEW.
>
> This means 2 things:
> 1) I cannot mix P_NEW and exact-number Read
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>>
>>>lo: another special data type. Is its functionality required
>>>anymore? It appears to be a workaround to some limitations of
>>>our large object interface which may no longer exist.
>
> I **think** the lo datatype is for ODBC binary access.
Andrew,
> userlocks is just a very thin interface to functionality that's really in
> the backend. What's left in contrib/userlock probably isn't even
> copyrightable in any case. The best bet is probably to re-implement it in
> the backend directly.
>
> Removing it certainly isn't a good idea; th
* Tom Lane <[EMAIL PROTECTED]> [07.06.2005 07:59]:
> Why bother? Just write each page when you need to --- there's no law
> that says you must use P_NEW.
This means 2 things:
1) I cannot mix P_NEW and exact-number ReadBuffer() calls;
2) thus, I have to track next-block-number myself.
Is it so?
> adddepend: is this still needed, or would a proper
> dump-and-reload from 7.2 add the dependancy information anyway?
No, a 7.2 to 7.3 or later upgrade will not have full dependency
information using pg_dump.
That said, I would abandon the module anyway. I don't recall testing it
for a 7.2 to 8.
lo: another special data type. Is its functionality required
anymore? It appears to be a workaround to some limitations of
our large object interface which may no longer exist.
I **think** the lo datatype is for ODBC binary access.
Sincerely,
Joshua D. Drake
--
Your PostgreSQL solutio
On Tue, Jun 07, 2005 at 02:53:32PM -0300, Josh Berkus wrote:
> Moving to PgFoundry is NOT "Demotion"
>
Yeah, I agree. Lots of people understand "search in pgfoundry.org" much
easily than "see contrib/adddepend". (I agree with most of the rest of
your com
On 2005-06-07, Josh Berkus wrote:
> userlocks: another GPL script, with the problems that entails.
> Also problematic as it relies heavily on per-record OIDs,
> something we tell users not to do. Overall, should be removed.
> Author: Massimo.
userlocks is just a very thin interface to function
On Tue, 2005-06-07 at 13:53, Josh Berkus wrote:
> mysql: these utilities have been moved to project sites (such as
> GBorg), and I believe that my2pg is broken with current versions
> of MySQL. Can we remove this from contrib?
>
I believe this version now lives at
http://gborg.postgresql.org/pro
Bruce Momjian wrote:
> Is this a direction we want to explore --- using the SONAME as part
> of the translation domain?
I think that's the way to go.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Don'
Bruce Momjian wrote:
> Uh, I thought the shoot-down was for duplication of existing
> information in new system tables, not the addition of new system
> table information, e.g. we have pg_operator, but no list of error
> codes or keywords in the system tables.
System tables are primarily useful if
FYI, I have results being generated daily against CVS, in addition to
dbt2:
http://developer.osdl.org/markw/postgrescvs/
I've also added a link to instructions on how to submit patches to test
against PostgreSQL on that page, if anyone's interested.
Thanks,
Mark
---
a few comments scattered inline...
On Tue, Jun 07, 2005 at 02:53:32PM -0300, Josh Berkus wrote:
> Folks,
>
> I had a lot of time to kill on airplanes recently so I've gone
> digging through /contrib in an effort to sort out what's in
> there and try to apply some consistent rules to it. Before
>
On Tue, Jun 07, 2005 at 12:42:47PM -0500, Scott Marlowe wrote:
> On Tue, 2005-06-07 at 12:16, Jaime Casanova wrote:
> > I suppose this is because the columns in the except are the same that
> > the ones in the main select and the order by get confused.
> >
> > i'm redirecting to hackers to know if
Folks,
I had a lot of time to kill on airplanes recently so I've gone
digging through /contrib in an effort to sort out what's in
there and try to apply some consistent rules to it. Before
people read further, please understand that this is just an
initial discussion on what will and won't be in
> SELECT encounter.encounter_id, encounter_d.encounter_d_id
> FROM encounter
> JOIN encounter_d on encounter_d.encounter_id = encounter.encounter_id
> EXCEPT
> SELECT encounter.encounter_id, encounter_d.encounter_d_id
> FROM encounter
> JOIN encounter_d on encounter_d.encounter_id = encounter.enco
[EMAIL PROTECTED] writes:
> I'm trying to copy the contents of a bucket of a hash table to a BufFile.
> There is a memory context for each bucket. That is, there is an array
> (#nbuckets) memory contexts.
That's a lot of contexts...
> The server terminated abnormally here "->>> (1)" at the code
hi,
I'm trying to copy the contents of a bucket of a hash table to a BufFile.
There is a memory context for each bucket. That is, there is an array
(#nbuckets) memory contexts.
thus the tree of mem cxts are
...
hashCxt
|
batchCxt
| |
| |
BucketCxt... BucketCxt
Bruce Momjian writes:
> What if we create a 'reset_connection' guc that is initially false, and
> is set to 'true' when someone resets a connection. Then, when it
> happens, the client finds out, reconfigures whatever it needs, then sets
> the value back to 'false'.
It seems to me that one could
On Tue, Jun 07, 2005 at 10:27:28PM +0900, Atsushi Ogawa wrote:
>
> David Fetter wrote:
> > On Tue, Jun 07, 2005 at 09:35:56AM +0900, a_ogawa wrote:
> > > David Fetter wrote:
> > > > We don't yet have this functionality, as the patch allows for
> > > > using second and later regex matches "()" in t
Our current RESET CONNECTION TODO item is:
* Add RESET CONNECTION command to reset all session state
This would include resetting of all variables (RESET ALL), dropping of
temporary tables, removing any NOTIFYs, cursors, open transactions,
prepared qu
Hi there,
I want to inform that we began to work on concurrency and recovery
support in GiST on our's own account and hope to be ready before 8.1
code freeze. There was some noise about possible sponsoring of our work,
but we didn't get any offering yet, so we're looking for sponsorhip !
We re
David Fetter wrote:
> On Tue, Jun 07, 2005 at 09:35:56AM +0900, a_ogawa wrote:
> > David Fetter wrote:
> > > We don't yet have this functionality, as the patch allows for
> > > using second and later regex matches "()" in the replacement
> > > pattern.
> > >
> > > The function is misnamed. It sho
Tom Lane wrote:
In the XLogInsert(), it makes two kinds of logs, "whole buffer(page)
log" and "partial buffer log", isn't it? Is it only "who buffer
log"
to generate a log with "hole"?
>
>>
>> Right.
I see.
I think, it is important to reduce the n
33 matches
Mail list logo
