On 2/6/12 3:19 PM, Bruce Momjian wrote:
> While we're waiting for anyone else to weigh in with an opinion on the
> right place to draw the line here, do you want to post an updated
> patch with the changes previously discussed?
Well, I think we have to ask not only how many people are using
f
On Jan 6, 2010, at 5:46 PM, Andrew Dunstan wrote:
> Tim Bunce wrote:
>> I was investigating a bug in an 8.4.1 production system and distilled a
>> test case down to this:
>>
>>CREATE OR REPLACE FUNCTION bar() RETURNS integer AS $$
>>#die 'BANG!'; # causes server process to exit(2)
>>
On Jan 6, 2010, at 1:52 AM, decibel wrote:
> On Dec 30, 2009, at 9:50 PM, Bruce Momjian wrote:
>> 3) There is no easy way to analyze all databases. vacuumdb --analyze
>> does analyze _and_ vacuum, which for an 8.4 to 8.5 migration does an
>> unnecessary vacuum. Right now I
On Dec 30, 2009, at 9:50 PM, Bruce Momjian wrote:
> 3) There is no easy way to analyze all databases. vacuumdb --analyze
> does analyze _and_ vacuum, which for an 8.4 to 8.5 migration does an
> unnecessary vacuum. Right now I recommend ANALYZE in every database,
> but it would be nice if there w
On Dec 29, 2009, at 6:29 PM, Tom Lane wrote:
> * when a tabstat message comes in, increment changes_since_analyze by
> the sum of t_tuples_inserted + t_tuples_updated + t_tuples_deleted;
>
> * when an analyze report message comes in, reset changes_since_analyze
> to zero.
If that's being added, c
On Dec 15, 2009, at 6:29 PM, Jeff Davis wrote:
> On Tue, 2009-12-15 at 18:06 -0600, decibel wrote:
>> Now that varlena's don't have an enormous fixed overhead, perhaps it's
>> worth looking at using them. Obviously some operations would be
>> slower, but for
On Dec 19, 2009, at 4:38 PM, Robert Haas wrote:
> On Sat, Dec 19, 2009 at 1:56 PM, Caleb Welton wrote:
>> I maintain that the approaches that inform the user that they have met that
>> condition via ALTER statement failures (Postgres/DB2/Microsoft Bound Views)
>> have certain advantages over data
On Dec 19, 2009, at 9:52 PM, Robert Haas wrote:
> On Sat, Dec 19, 2009 at 10:46 PM, Bruce Momjian wrote:
>> Tom Lane wrote:
Bruce Momjian wrote:
> Seems I need some help here.
>>>
>>> I'm willing to work on this --- it doesn't look particularly fun but
>>> we really need it.
>>
>> You d
On Dec 22, 2009, at 12:54 PM, Simon Riggs wrote:
> 9. Create a recovery command file in the standby server with parameters
> required for streaming replication.
>
> 7. (a) Make a base backup of minimal essential files from primary
> server, load this data onto the standby.
>
> 10. Start postgres
On Dec 15, 2009, at 11:34 AM, Jeff Davis wrote:
> On Tue, 2009-12-15 at 10:19 -0500, Tom Lane wrote:
>> I'm not sure that anyone has argued that. I did suggest that there
>> might be a small list of types for which we should provide discrete
>> behavior (ie, with next/previous functions) and the r
On Dec 15, 2009, at 5:40 PM, Jeff Davis wrote:
> If you think I'm proposing that we drop inclusivity/exclusivity before
> telling the application, that's not what I'm proposing at all. I'm
> proposing that, at least in some circumstances, it's important to be
> able to display the same value in dif
On Dec 11, 2009, at 8:44 PM, Tom Lane wrote:
> Bruce Momjian writes:
>> Ashish wrote:
>>> I am thinking about starting with the following TODO item:
>>> --> Have EXPLAIN ANALYZE issue NOTICE messages when the estimated
>>> and actual row counts differ by a specified percentage.
>
>> I even have a
On Dec 3, 2009, at 1:53 PM, Jonah H. Harris wrote:
On Tue, Dec 1, 2009 at 1:27 PM, Joshua D. Drake
wrote:
On Tue, 2009-12-01 at 13:20 -0500, Robert Haas wrote:
> Does $COMPETITOR offer this feature?
>
My understanding is that MSSQL does. I am not sure about Oracle. Those
are the only two I ru
On Dec 1, 2009, at 4:13 PM, Greg Stark wrote:
On Tue, Dec 1, 2009 at 9:57 PM, Richard Huxton
wrote:
Why are we writing out the hint bits to disk anyway? Is it really so
slow to calculate them on read + cache them that it's worth all this
trouble? Are they not also to blame for the "write my im
On Dec 1, 2009, at 1:39 PM, Kevin Grittner wrote:
Josh Berkus wrote:
And a lot of our biggest users are having issues; it seems pretty
much guarenteed that if you have more than 20 postgres servers, at
least one of them will have bad memory, bad RAID and/or a bad
driver.
Huh?!? We have abou
On Dec 1, 2009, at 12:58 PM, Tom Lane wrote:
The bottom line here seems to be that the only practical way to do
anything like this is to move the hint bits into their own area of
the page, and then exclude them from the CRC. Are we prepared to
once again blow off any hope of in-place update for
s extremely unlikely you would intentionally want the same hint to
apply to a bunch of queries, and extremely likely that you could
accidentally forget to re-enable something.
That said, thanks for contributing this!
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give
of
overhead, it would be nice to keep that in mind. I don't know where
something like randomly reseting the search would go in the code, but
I suspect it wouldn't be very expandable in the future.
But like Tom said, the top goal here is to help deal with bloat, not
other f
On Sep 30, 2009, at 5:13 PM, Kevin Grittner wrote:
decibel wrote:
*any* step that improves dealing with table bloat is extremely
welcome, as right now you're basically stuck rebuilding the table.
+1
Although, possibly more irritating than actually rebuilding it is
evaluating borde
t won't
lead to desirable tab-completion behavior. OTOH, we have
survived with pg_index vs pg_indexes, so maybe it wouldn't
kill us.
Another option is to revisit the set of system views (http://
pgfoundry.org/projects/newsysviews/). IIRC there was some other
recent reason we wante
the lock that's needed to trim the
file on disk.
That said, *any* step that improves dealing with table bloat is
extremely welcome, as right now you're basically stuck rebuilding the
table.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer so
h sprintf, but only
because everything is referencing the same field.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
know I've created a function that does that (though, I
return a cased string, since it's easier to run it through lower than
to try and case it after the fact). I'm not sure if a function is the
best way to do this or if a table or view would be better (something
you coul
On Sep 14, 2009, at 12:13 AM, Pavel Stehule wrote:
2009/9/13 decibel :
On Sep 12, 2009, at 5:54 PM, Andrew Dunstan wrote:
decibel wrote:
Speaking of concatenation...
Something I find sorely missing in plpgsql is the ability to put
variables inside of a string, ie:
DECLARE
v_table text
On Sep 12, 2009, at 5:54 PM, Andrew Dunstan wrote:
decibel wrote:
Speaking of concatenation...
Something I find sorely missing in plpgsql is the ability to put
variables inside of a string, ie:
DECLARE
v_table text := ...
v_sql text;
BEGIN
v_sql := "SELECT * FROM $v_table";
Of c
missing in plpgsql is the ability to put
variables inside of a string, ie:
DECLARE
v_table text := ...
v_sql text;
BEGIN
v_sql := "SELECT * FROM $v_table";
Of course, I'm assuming that if it was easy to do that it would be
done already... but I thought I'd just throw it out th
ith the idea of anyelement(N) might be a lot more
practical...
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to yo
that should be providing a means to determine what the
underlying type of an "any" is. Having that would allow functions to
take actions appropriate to different types.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.d
is), (ref)objid into an
actual object name, and (ref)objsubid into a real name.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
al-world case we have are updatable views on top of a
union. In this case we'd want the result to reflect the updates that
occurred in all the tables, not just in the last table in the rule.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some br
ally help for SELECT *...
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ther. IE: hard-coded guesses have a low confidence.
Something pulled right out of most_common_vals has a high confidence.
Something estimated via a bucket is in-between, and perhaps adjusted
by the number of tuples.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Giv
n cost/row threshold, we just run with
that plan. If not, we go back and do a more detailed estimate.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgs
it should get killed off.
I believe it's useful when dealing with very bloated relations. If
someone's looking for an itch to scratch, ways to more effectively
shrink bloated relations would be good.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
NGUAGE plpgsql AS $exec$
BEGIN
RAISE DEBUG 'Executing dynamic sql: %', sql;
EXECUTE sql;
IF echo THEN
RETURN sql;
ELSE
RETURN NULL;
END IF;
END;
$exec$;
The echo parameter is sometimes useful in scripts so you have some
idea what's going on; but i
d be made for base64 encoded data.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.pos
ical size of your data that's being toasted? I actually
have a number of cases where I'd like to push data into external
storage, because it seriously hurts tuple density (and I doubt it'd
compress well).
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.or
an be worthwhile to some?
Here's an off-the-wall thought... since most of the CPU time is in
the sort, what about allowing a backend to fork off dedicated sort
processes? Aside from building multiple indexes at once, that
functionality could also be useful in general queries.
--
Decibel!,
nceivably be called from other languages, such
as plPerl.
But it sounds like this can be done via an add-on, so no need to add
it directly to the backend.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #182
ome out of users too (not this exact case, but similar).
Perhaps what we really want is an "optimization level" GUC so that
users can tell the backend how much overhead they want the optimizer
to spend on trying to work around stupidity... :)
--
Decibel!, aka Jim C. Nasby, Data
nk that's almost always been because RAISE
DEBUG doesn't provide that context.
So, if it makes it easier, we could probably get by with just the
function that called us. Another possible option would be if there
was a way to get our function name (which we could then pass on to
or machine-
created events. If you want to present it all as one, I suggest a
union view that turns the machine-understood data into a human-
understandable text format.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distrib
On May 27, 2009, at 11:31 AM, decibel wrote:
It does seem somewhat useful to be able to analyze all databases
easily from the command-line, but putting it into vacuumdb is
certainly a hack.
So... do we want a completely separate analyzedb command? That
seems like far overkill.
Arguably there
Sure, pg_migrator is what started this, but it's completely
orthogonal to the lack of a "analyze everything" command.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via
ons, which I'm thinking should go in the function rather than
in the option parsing section. But I didn't want to put any more
effort into this if it's not something we actually want.
patch
Description: Binary data
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decib
On May 19, 2009, at 10:52 AM, Robert Haas wrote:
How 'bout we flip that around? :-)
+1
(BTW, I know there's pg_dump, but being able to get SQL out of psql
is just a lot more convenient)
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer
default to be all-tabular output, but had
a different command that would spit out the SQL to re-create something?
(I agree that the cut-and-paste ability is extremely handy and
wouldn't want to remove it.)
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your com
On May 18, 2009, at 10:25 PM, Tom Lane wrote:
decibel writes:
The gripe I have with \d is that the "footnotes" are very hard to
scan through once you have more than a few things on a table. What
I'd like to see is a version that provides the same information, but
in a tabula
is, but I could
probably get CashNetUSA to pay to have it done. :)
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
cessing
(assuming that would even work). But if I knew what the previous
query was, I'd at least have half a chance to know what portion of
the code was responsible, and could then look at the code to see if
the idle state was expected or not.
--
Decibel!, aka Jim C. Nasby, Database
take into
account the new updatable views, you're still hosed if you add a
column to the table. I see that being a lot more useful than a simple
column alias (you're correct that we'd need to support calculated
ones, which is indeed a lot harder).
--
Decibel!, aka Jim
efore.
Unless they haven't realized that we've been pulling a MySQL and
silently truncating their data. :(
On another point, I agree that compression would be nice, and the way
to fix that is to expose knobs for controlling TOAST thresholds
(something I've wanted forever
ially at the table level) would be handy.
And +1 on reviving newsysviews, but of course I'm biased... ;P
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgs
actually faster to use an
index. The bitmap case is even more interesting. Something is
seriously screwy with small seqscans it seems.
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent
Thought folks might get a kick out of this since he's referenced all
over our code: http://www.appelbaum.net/
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing
m would probably be a lot better than
what we have now. I'm guessing that there are a lot of databases where
either the whole database fits in cache, or a decent chunk of
relatively small core relations fit in cache and then there are some
big or infrequently-used ones that don't.
--
De
t the constraint name?
Though, that wouldn't be quite enough if you did:
CREATE TABLE a(a_id ...)
CREATE TABLE b(.., a_id int not null, foreign key(id) references a(id))
Handling that would require passing something into
transformColumnNameList() to tell it if it was checking fk_attrs vs
edIn: http://www.linkedin.com/in/carlosgonzalezcadenas
On Thu, Jan 22, 2009 at 7:16 PM, decibel wrote:
On Jan 22, 2009, at 8:24 AM, Euler Taveira de Oliveira wrote:
No one that I know of. Well, it is a long road. The addition of a
data type
xml is recent (8.3). We lack a set of features like i
o the same location you'll trash everything. I
don't know of a good work-around; IIRC we used to leave the archive
command to complete, but that could seriously delay shutdown so it
was changed. I don't think we created an option to control that
behavior.
--
Decibel!, a
ch of
these TODO items completed before the next two releases (unless you
want to
take a stab).
You could also possibly pay a consulting company to implement it, but
even that isn't as easy as it may sound. :)
--
Decibel!, aka Jim C. Nasby, Database Architect deci...@decibel.org
Give you
e at 100+MB/s. Typically, we're pushing ~5MB/s, but
during recovery we'll only do 600-700kB/s. I've never straced a
backend to see exactly what's going on.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.
N add(
a int
, b int
) TO someuser;
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
part of
this at a time. There would be value in only allowing logical order
to differ from literal order, or only allowing physical order to
differ. That means you could tackle just one of those for the first
go-round and still get a benefit from it.
--
Decibel!, aka Jim C. Nasby, Dat
that are
being impacted by our ultra-low stats target, and a lot of those
don't necessarily need a lot of hand tuning beyond the stats target.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent
se before
worrying about additional stats to collect. :)
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to you
#x27;s not even true; you still have to
eventually freeze a write-mostly table.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
teed to
be better than 10, even if it's nowhere close to an ideal value. If
we start slowly increasing it then at least we can start seeing where
people start having issues with query plan time.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer so
you are that such a feature is incapable of causing
problems.
IIRC the community did come to a consensus on allowing for a
different logical ordering from physical ordering, it was an issue of
actually doing the work. If this is an itch you want to scratch, you
might look into fixing t
nd such a view would suddenly
become updateable.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http:
On Nov 9, 2008, at 11:44 AM, Tom Lane wrote:
Decibel! <[EMAIL PROTECTED]> writes:
On Nov 8, 2008, at 3:08 PM, Tom Lane wrote:
... It's reasonably common for pg_xlog to be a symlink.
ISTM it'd be better still to have an official knob that allows you to
determine where pg_
question. Why is this needed at all?
I suspect this is to deal with needing to reserve space in a cluster
that you're planning on upgrading to a new version that would take
more space, but I think the implementation is probably too simplistic.
--
Decibel!, aka Jim C. Nasby, Database Archi
be specified as re-writable
t { display: table-row }
¶t1, ¶t2, ¶t3 { display: table-cell input} /* read-write */
if user cannot update database field
REVOKE update ON t FOR user1;
then corresponding xml-attribute will be specified as read-only
t { display: ta
-
defined dimension means, but I can't see how the results of that
should vary between array_length and array_lower/upper.
Is there some other corner case?
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team
t into 8.4 and
possibly paint ourselves into a corner, or should we just wait until
8.5?
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
d be better to store this information in a separate table, or
maybe a separate file. That might be best anyway; we generally
wouldn't need this information, so it would be nice if it wasn't
bloating pg_class all the time.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAI
ee anything obvious in postgresql.conf or configure.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
if (! TRIGGER_FIRED_FOR_ROW(trigdata->tg_event))
+ elog(ERROR, "min_update_trigger: not called for each row");
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
mated
separately, and the executor would favor executing the cheaper one
first.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
On Oct 24, 2008, at 7:19 PM, Tom Lane wrote:
Decibel! <[EMAIL PROTECTED]> writes:
Was anything ever done with http://archives.postgresql.org/pgsql-
hackers/2008-09/msg01758.php ?
No, we got stalled on what the behavior really ought to be:
http://archives.postgresql.org/pgsql-hackers/2
Next installment: id = , installment_date =
NOT v_prev IS NULL = t, v_prev IS NULL = f
NOT v_next IS NULL = f, v_next IS NULL = t
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net T
On Oct 21, 2008, at 12:06 PM, Tom Lane wrote:
"Jim 'Decibel!' Nasby" <[EMAIL PROTECTED]> writes:
WHERE 'xxx' IN (people.home_phone, people.work_phone,
people.mobile_phone)
Yeah, not exactly a common case, but at least in 8.1 this was turne
::text = ANY ((ARRAY[home_phone, mobile_phone,
work_phone])::text[]))
Which means automatic seqscan. Would it be difficult to teach the
planner to handle this case differently? I know it's probably not
terribly common, but it is very useful.
--
Decibel! [EMAIL PROTECTED] (512) 569-9
On Oct 17, 2008, at 4:30 AM, Vladimir Sitnikov wrote:
Decibel! <[EMAIL PROTECTED]> wrote:
I had tried to use a normal table for store stats information,
but several acrobatic hacks are needed to keep performance.
I guess it is not really required to synchronize the stats into
some ph
suggest either rolling up your sleeves or dangling a carrot (money)
in front of some of the people that do consulting and back-end hacking.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Des
orkload OLTP or OLAP? Promoting seqscans in an OLTP
environment seems to be a really bad idea to me...
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
sive LOG entries, they won't be
so blind. I think just adding the HINT is good enough.
Since this is something that's not supposed to happen, making it a
WARNING might be appropriate too...
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your
-run shared memory pretty quickly if you had a lot of different
queries you were running.
Of course, someone could always just setup a cron job to grab the
stats once a minute, so if this greatly complicates the patch I
wouldn't worry about it.
--
Decibel!, aka Jim C. Nasby, Database Arc
ISTM it'd be useful to have an array_length function (since I just
wrote one for work ;), so here's a patch. Note that I don't have the
docs toolchain setup, so I wasn't able to test the doc patches.
array_length.patch
Description: Binary data
--
Decibel!, aka Ji
sting. Perhaps default to assuming a good format and only fail
back to something else if that doesn't work?
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
be sensible if we support this aspect as
well.
+1. And for everyone who immediately jumped to "NORMALIZE!" as the
answer, consider that that means a bare minimum of 24 bytes overhead
per item that would go into the array. It's not hard at all for that
overhead to become ma
byte per digit. Some concept of data type for an attribute would
improve this.
Sadly, I don't have time to work on any of this. But these things are
issues to my company, and we do have money. ;)
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some br
On Oct 1, 2008, at 12:12 AM, Gurjeet Singh wrote:
On Wed, Oct 1, 2008 at 9:39 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
"Gurjeet Singh" <[EMAIL PROTECTED]> writes:
> On Wed, Oct 1, 2008 at 3:07 AM, Decibel! <[EMAIL PROTECTED]>
wrote:
>> ERROR: aggregates n
em to use the oid instead like we do
with
pg_class.
It would be really nice to have the table OID in pg_tables. That was
one of the driving forces behind the pg_newsysviews project.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain
T 0,
only because we don't want to define formal optimizer hints (and
that's *exactly* what OFFSET 0 is).
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
On Oct 5, 2008, at 8:50 PM, Greg Smith wrote:
Patch v3 attached that exposes boot_val and reset_val. The docs
for the latter link to the RESET command page for details.
Is it really that important that we save 2 characters on
each field name?
--
Decibel!, aka Jim C. Nasby, Database
sums on a block the first
time we touched it during recovery, we'd be able to detect torn
pages, yet still recover. That would help show that torn pages aren't
possible in a particular environment (though unfortunately I don't
think there's any way to actually prove that
y and get it in for 8.4.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
eate a full test case for this...
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
7;re now exposing
yourself to the possibility of issues with the FS itself. Not to
mention that changing filesystems on a large production system is
very painful.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #18
non-invasive as possible. And
it would be really nice if this could be enabled without a dump/
reload (maybe the upgrade stuff would make this possible?)
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
1 - 100 of 296 matches
Mail list logo
