rt, too, where additional, unindexed columns
> are stored alongside indexed columns.
>
> And I wonder if it would work well with expressions, too?
>
> David
IRC MS SQL also allow unindexed columns in the index.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mai
use it was 1kb behind in reading logs
from the master. If the new master could deliver the last bit of the
old masters logs that would be very nice.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Feb 27, 2012 at 11:54 PM, Andrea Suisani wrote:
> On 02/28/2012 04:52 AM, Rob Wultsch wrote:
>>
>> On Wed, Feb 22, 2012 at 2:31 PM, james
>> wrote:
>>>
>>> Has anyone considered managing a system like the DragonFLY swapcache for
>>
On Wed, Feb 22, 2012 at 2:31 PM, james wrote:
> Has anyone considered managing a system like the DragonFLY swapcache for a
> DBMS like PostgreSQL?
>
https://www.facebook.com/note.php?note_id=388112370932
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsq
comparison. I have seen this sort of
things cause significant production issues several times.*
I have seen several companies use comparisons of dissimilar data types
as part of their stump the prospective DBA test and they stump lots of
folks.
--
Rob Wultsch
wult...@gmail.com
--
Sent
ber of writes is potentially
halving the life of the flash.
Something to think about...
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ect statement for all the fields in a given table,
> with an optional alias prefix.
>
> For the purposes of pg_dump, perhaps we'd want to move all the getFoo()
> functions in pg_dump.c into the library, along with a couple of bits from
> common.c like getSchemaData().
&g
On Fri, May 6, 2011 at 2:47 PM, Robert Haas wrote:
> Comments?
At my day job there is saying: "Silence is consent".
I am surprised there has not been more discussion of this change,
considering the magnitude of the possibilities it unlocks.
--
Rob Wultsch
wult...@gmail.com
On Wed, Jan 5, 2011 at 7:48 AM, David Fetter wrote:
> On Wed, Jan 05, 2011 at 09:04:08AM -0500, Robert Haas wrote:
>> On Tue, Jan 4, 2011 at 10:56 PM, Rob Wultsch wrote:
>> > 1. Could the making a table logged be a non-exclusive lock if the
>> > ALTER is allowe
it on the master), skip step #6, and do step #7
> backwards.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
A couple thoughts:
1. Could the making a table logged be a non-exclusive lock if the
ALTER is allowed to take a full ch
On Wed, Dec 22, 2010 at 12:15 AM, Heikki Linnakangas
wrote:
> On 22.12.2010 03:45, Rob Wultsch wrote:
>>
>> On Tue, Dec 21, 2010 at 4:49 AM, Robert Haas
>> wrote:
>>>
>>> On Sun, Dec 19, 2010 at 1:10 PM, Jim Nasby wrote:
>>>>
>
://forge.mysql.com/worklog/task.php?id=4925
http://www.facebook.com/note.php?note_id=194501560932
Also, InnoDB has an option for how much data should be allocated at
the end of a tablespace when it needs to grow:
http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#sysvar_innodb_data_fil
On Sun, Dec 12, 2010 at 7:33 PM, Robert Haas wrote:
> On Sun, Dec 12, 2010 at 9:31 PM, Rob Wultsch wrote:
>> On Fri, Dec 10, 2010 at 5:34 PM, Cédric Villemain
>> wrote:
>>> 2010/12/8 Kineticode Billing :
>>>> On Dec 8, 2010, at 10:37 AM, Chris Browne w
fact that fk checks are implemented by the trigger system somehow
seems "surprising".
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, Dec 10, 2010 at 5:34 PM, Cédric Villemain
wrote:
> 2010/12/8 Kineticode Billing :
>> On Dec 8, 2010, at 10:37 AM, Chris Browne wrote:
>>
>>> Other possibilities include TRANSIENT, EPHEMERAL, TRANSIENT, TENUOUS.
>>
>> EVANESCENT.
>
> UNSAFE ?
>
own to hold, there's a real chance the
> DBA will be backed into a corner where he simply has no choice but to
> not use foreign keys, even though he might really want to validate the
> foreign-key relationships on a going-forward basis.
>
> --
> Robert Haas
> EnterpriseDB: http
On Sun, Dec 5, 2010 at 6:59 PM, Robert Haas wrote:
> On Sun, Dec 5, 2010 at 2:45 PM, Rob Wultsch wrote:
>> I think you have read a bit more into what I have said than is
>> correct. MySQL can deal with thousands of users and separate schemas
>> on commodity hardware.
--
> Greg Smith 2ndQuadrant US g...@2ndquadrant.com Baltimore, MD
> PostgreSQL Training, Services and Support www.2ndQuadrant.us
>
Forgive me, but is all of this a step on the slippery slope to
direction io? And is this a bad thing?
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sun, Dec 5, 2010 at 12:45 PM, Rob Wultsch wrote:
> One thing I would suggest that the PG community keeps in mind while
> talking about built in connection process caching, is that it is very
> nice feature for memory leaks caused by a connection to not exist for
> and continue gro
ver.
NOTE: 100k is not a number that I would put much stock in. I don't
recall ever mentioning that number and it is not a number that would
be truthful for me to throw out.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
able SELECT statements that
probably need to examine more than 1,000,000 row combinations."
I have actually suggested that a certain subset of my users only
connect to the database if they are willing to use the --i-am-a-dummy
flag.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hac
t; Regards,
> Marti
>
++
I have a lot of DELETE with LIMIT in my (mysql) environment for this reason.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
s feature should be optional.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ore, and all of it will happen again."
At this point pg has the equivalent of MySQL's "show slave status" in
4.0. The output of that change significantly over time:
http://dev.mysql.com/doc/refman/4.1/en/show-slave-status.html
http://dev.mysql.com/doc/refman/5.5/en/show-slave-s
fail to start
> at all if we just changed the default for max_wal_senders and not the
> default for wal_level.
>
> regards, tom lane
If the variable is altered such that it is dynamic, could it not be
updated by the postmaster when a connection attempts to begin
replic
#x27;s not easy to address that problem.
> So I'm worried about that implementing that capability first means the miss
> of sync rep in 9.1.
>
> Regards,
>
> --
> Fujii Masao
> NIPPON TELEGRAPH AND TELEPHONE CORPORATION
> NTT Open Source Software Center
>
>
hings I really like about drizzle is if there a missing
dependency it will explicitly tell you what you are missing and where
to go find it for popular platforms.
Not being able to easily build is a barrier to entry. Does pg want those?
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hacker
the table to a very small number (or zero) number
of pages? Is there a case to be made for instead somehow marking all pages
as available for reuse? Deallocating and reallocating space can be
expensive.
--
Rob Wultsch
wult...@gmail.com
hich is the primary trigger for
> autovacuum vacuum freezing. I have added the attached documentation
> patch for autovacuum_freeze_max_age; back-patched to 9.0.
>
> --
> Bruce Momjian http://momjian.us
> EnterpriseDB http://enter
formation_schema. ones arent complete enough and have enough concept
> mismatch to be confusing. But why all this?
>
> Andres
>
Do you have an alternative suggestion for emulating
"SHOW SCHEMAS"
"SHOW TABLES"
"DESC object"?
Make a user friendly interface i
On Fri, Jul 16, 2010 at 10:52 AM, Heikki Linnakangas
wrote:
> On 16/07/10 20:11, Rob Wultsch wrote:
>>
>> On Fri, Jul 16, 2010 at 9:56 AM, Robert Haas
>> wrote:
>>>
>>> For committers.
>>
>> Perhaps this discussions should be moved to the Gene
hat followed caused that idea to scrapped.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
significant size that interact with MySQL have errors because of this
issue and it would be good to not claim to have made Postgres
compatible.
That said, I imagine if this feature could make it into the Postgres
tree it would be very useful.
Would I be correct in assuming that while this feature
On Fri, May 14, 2010 at 11:50 PM, Rob Wultsch wrote:
>> Linux has *as many if not more* ... MySQL, if memory servers, has a half
>> dozen or more ... etc ...
>
> MySQL has a bunch of lists, none of which get much traffic. Honestly,
> they should probably be combined.
>
&
On Sat, May 15, 2010 at 4:09 AM, Kevin Grittner
wrote:
> Anything in particular you wanted me to notice about it besides that?
Nope. It was just a counter point to your previous comment.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.
On Fri, May 14, 2010 at 7:32 AM, Kevin Grittner
wrote:
> Oracle, and all other MVCC databases I've read about outside of PostgreSQL,
> use
> an "update in place with a rollback log" technique.
Have you looked at PBXT (which is explicitly NOT SERIALIZABLE)?
--
Rob W
> Linux has *as many if not more* ... MySQL, if memory servers, has a half
> dozen or more ... etc ...
MySQL has a bunch of lists, none of which get much traffic. Honestly,
they should probably be combined.
--
Rob Wultsch
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgres
ity to
determine *easily* how much a slave is lagging in clock time.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
he gets a call at
3AM that a server
(p3.any43.db69.I_have_no_clue_what_this_stupid_f'ing_server_is.wtf.pg
) is at max-connections. I think that some helpful hints for non-pg
dba's that are using pg in some capacity are a very good idea.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
else if (MYSQL_HELP_CHECK("show processlist"))
+ {
+ MYSQL_HELP_OUTPUT("SELECT * from
pg_stat_activity");
+ }
+ else if (MYSQL_HELP_CHECK("desc"))
+ {
+
onstraints, and a MySQL
> blog hinted some time ago that it might be in SQL 201x.
>
> --
> Alvaro Herrera http://www.CommandPrompt.com/
> The PostgreSQL Company - Command Prompt, Inc.
The mysql'ism foreign_key_checks would seem to do similar things...?
(http://dev.mysql.co
gs nor the bad designs decisions from
> MySQL, no that everything from MySQL is bad but i would be scary if we
> start supporting every single piece of code MySQL accepts
>
And that behavior has changed to be sane in 5.0+, iirc.
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hac
On Tue, Aug 25, 2009 at 10:36 AM, Pavel Stehule wrote:
> 2009/8/25 Rob Wultsch :
>> Given the recent discussion of "DELETE syntax on JOINS" I thought it
>> might be interesting to bring a bit MySQL syntax that is in somewhat
>> widespread use, generally create some
13='val13',
col14='val14',
col15='val15';
Which I think sometimes compares very favorably
INSERT INTO t
(col1,col2,col3,col4,col5,col6,col7,col8,col9,col10,col11,col12,col13,col14,col15)
VALUES
('val1','val2','val3','val4'
44 matches
Mail list logo
