text:
24 February, 2011
1x10 Experiment
For shifting I've set up most of my road bikes with 9 or 10-speed Campy brifters. I know there is still some resistance to index-shifting among the retro crowd, but I've been using it since the 1990's without issue. I've also had no issues with 10-speed drive trains.
So what's the experiment? Well, I've noticed that 1x10 drive trains are starting to appear on more and more mountain bikes. Shimano is making wide range 10-speed cassettes, 11t-36t. I wonder how a 1x10 drive train would work on a rando or touring bike? I think I'll build something along those lines later this year. Anyone have any experience with 1x10 on the road, or any thoughts?
Posted by Velo Orange at 11:19:00 AM
49 comments:
- Unknown said...
Nice 2CV!
- Spencer Morse said...
I use Dura-Ace 10-speed indexed downtube shifters on my Salsa Casseroll. I do run a triple crank, but rarely am out of the 39t ring. But I do live in Wisconsin. In Utah, where I'm from, the 30t was VERY welcome. The new SRAM APEX cassette and derailleur setup could work nicely with a 1x10 road setup. I like the idea of simplifying.
- Groundshine said...
How about 1x8? I rode last year's Fleche on a 1x8 internal gear. Performs great in the rain compared to a derailleur bike. I enjoy the large steps between gears during long distance rides. Would prefer even larger than what the Alfine provides...
- dr2chase said...
No experience with a 1x10, but some with a 9-speed IGH (SRAM) and some with an 8-speed IGH (Alfine). 11-36 gives you a 327% range, midway between the Alfine (307%) and SRAM (340%) ranges.
The kicker is, I'm riding a cargo bike, and in warmer months often climb short hills with 400lbs GVW, and have gone as high as 450lbs GVW (heavy passenger). The compromise made is to set the range as low as possible; with the Alfine (I broke the SRAM), I am often in one of the top two gears -- highest gear-inches is 83. If I "need" a higher gear, I either spin, or coast. Low is about 27 gear-inches (1:1 into a 26x2.35" tire).
It seems to me this would work for a non-cargo bike, too. - 2/24/11, 11:46 AM
- Unknown said...
I think it sounds like a great idea. Simple yet effective. I've seen a number of cyclocross setups running a single chain ring as well. If nothing else end up with stronger legs!
- Anonymous said...
I'm of two minds on this. I rode a 1x6 (47x14-28) with no chainguard ring or guide on the inside for a long time on a light tourer I used as a city errand bike and long haul commuter and couldn't have been happier in the relatively flat midwest. I could make it drop the chain if I did everything wrong in just the right way, but I probably got more flats than dropped chains on that bike.
There are tons of people lining up at cross races these days with 1x10 setups, but they all run chainguards and chain guides. I'm sure you could find some magic combination of high-toothed chainring, perfect chainline, and optimal RD spring tension that wouldn't drop the chain, but I think I'd want guards and guides. It's one thing for racers who have decided they simply don't want or need to shift in the front, but for a recreational bike building it up turns into an exercise in elaborate minimalism. You end up buying some combination of a chainguard ring, an inboard chain guide, a new chainring, a shifter you don't end up using, and maybe even some extra brake levers. Some of us could do that out of our parts bins without even going to the basement, but it's always a little goofy. You can also use the Paul guide or cannibalize an old FD for the guide, but the Paul part costs as much as a good FD and looks like something that fell off an M-16 (not always a bad thing but not really the popular aesthetic around here). When the smoke clears on these builds it just ends up being a ton of work and parts without any real benefit. - 2/24/11, 12:03 PM
- stevep33 said...
Agreed that without a front der, you would be happy to have a guide of some sort to prevent the chain from hopping off the ring on a big pothole or something.
There are many doodads out there, but I've been pretty happy with a cheap BGB bach guard replacing the outer ring of a double crank. a 42T ring with a 11-34 cassette gives you all the gears you need and reasonable chainline for the popular gears. The added bonus of a bash guard over a top side guide is that you won't have the chain bumping upwards against a guide when in the largest cog from a modestly sized chainring. - 2/24/11, 12:42 PM
- stevep33 said...
btw, that Pass Hunter is still one of my favorites. Stunning.
- Anonymous said...
I rode a 1x9 road bike for a couple of years, with a 11-32 on the back and a 42 or a 52 on the front. The gear range is totally fine for Manayunk & the Philly area, where I live. The shifting is also nice & logical & easy---just the one control to remember.
But there's no weight or cost savings to such a setup in my experience. You have to A) run a bashguard or a bigger chainring outside, and a chain watcher inside, or B) dummy up a front derailleur to hold the chain on the front ring. Plus the chainline is terrible in the big & small gears, and I think I exacerbated an autoshifting problem on that frame too.
I might feel differently about my 1x9 experience if anyone made bashguards in sizes bigger than cyclocrossers use, but when I wanted to run a 52 ring on the front I ended up having to buy a cheap TT ring as my bashguard. - 2/24/11, 1:08 PM
- Alan@EcoVelo said...
I've been riding a 1x9 derailleur drivetrain on my commuter since August of last year. I'm running a Sugino track crank up front and a wide range cassette in back with a long-cage XT derailleur mated to a Paul Thumbie/DA bar-end shifter in friction mode. It's a clean, simple, and effective set-up for the flat to rolling terrain in which I ride. More here:
Alan@EcoVelo - 2/24/11, 1:08 PM
- mattcook said...
I'm with the anonymous guy. I rode 1x6 in madison, wi and the gearing worked great (even went on a week long camping trip with it) but you're gonna drop your chain without a guide. I know I did, about once a week. And you've maybe got a wonky extra unoccupied shifter braze on. You probably don't have to get too elaborate, just get a singlespeed crank with a guide if your aesthetic tastes allow.
But for practical, trouble free riding, unguarded 1x? ain't the way to go. I've satisfied my curiosity and I'll be going back to a traditional setup. - 2/24/11, 1:13 PM
- Janice in GA said...
I was real close to buying a 1x9 bike for a commuter last year. I think with the right range that that could work really well around town here.
I ended up with a 3x9 touring bike instead, though. I liked the shifters better, and I thought it might be more versatile for me. - 2/24/11, 1:28 PM
- Anonymous said...
My setup is 1x9, no guards, sunrace thumbshifter, no chain jump going on severe washboard roads and single-track besides daily road use. Even for extended touring I wouldn't change a thing. Go for it and keep it simple and fun.
- Interstatement said...
I've been thinking about doing a 1x10 city bike using a 1970's road frame. I have a like-new Univega Safari 10 frame that would have the added bonus of an appropriate name. As a city bike, a chainguard could assume chain-keeping duties with proper tweaking.
- Etherhuffer said...
Well, I like Rivendell's "7 is heaven' thinking. My 3x7 is just fine, but I rarely use the big ring in front. So a wide range rear set with a 40/30 ish range up front should be plenty as well.
My wife is a dreadful cross chainer, and I am thinking of getting rid of her triple and putting on a double up front to help end that. - 2/24/11, 2:06 PM
- Anonymous said...
I run a 1 x 7 on an old Schwinn Continental as a commuter. 46-tooth up front and something like 13 - 28 in back. I use an old front derailer to keep the chain in place. It works fine for a commuter, but a better shifting 1 x 10 would be an upgrade. Beautiful bike, by the way.
--Tom - 2/24/11, 2:18 PM
- Stevecrowley said...
I tried this when I was building up my girlfriend's Peugeot. It was a 1x6. I scrapped that idea right away because I couldn't even get it adjusted right in the workstand without the chain falling off of the ring. I didn't have a chain guide, but I did have everything I needed to set it up with a front der. so I just went with that. Definitely try it out, but be warned that you will definitely need some kind of chain keeper like the one that Paul makes.
- Unknown said...
My Vaya has a 1x10 set up on it and I love it. Going up some local hills I "sometimes" wish I had a 2x, but that thought passes as soon as I hit the crest!
- Mark S. said...
I ride a 1x10 on my Co-Motion Co-Pilot S&S travel bike. I have it set up with a 44 tooth chainring, an 11x32 rear cassette, and SRAM Apex long cage rear derailleur and right brifter. It gives me plenty of gears for any terrain. It also makes packing and travel easier - there are fewer cables and the 44 tooth ring protrudes less when packing the bike, particularly since it's covered by a bash guard. The worst part of the setup is the fairly large gap (13%) between the 44x15 and the 44x17. The chainline has been no problem. Good luck with yours!
- TraceO said...
I too have been commuting on a 1x8 drivetrain for the past 5 years. My set up is a bar-end shifter and a 25 year old Campy rear derailluer. I run the old Campy rear derailleur because of its super strong return spring which keeps more tension on the chain than modern derailluers do. I have yet to toss a chain with this set up.
- Anonymous said...
I've had a couple 1xMulti setups, used primarily in the city. They are awesome: it simplifies shifting psychologically. Currently my beater is rolling with a 1x9, 44 in the front and a 11-23 road cassette I had in the parts bin. Friction bar-end shifter, I've done a single down-tube shifter as well. If I hadn't had that laying around i'd have gone with something wide-range, but 44:23 is adequately low for someone who is used to cranking up hills on a singlespeed.
My thought on dropping chains & chain guides: with a wider range and a 42t road chainring meant for shifting, I dropped chain fairly frequently. However my current setup seems drop-proof even without a chain guide: with the tighter cassette and a tall-toothed 3/32" track chainring i have not had any problem, even dorking around offroad. - 2/24/11, 3:25 PM
- stevep33 said...
Is your jump-free unguarded 1x9 coupled with a narrow range cassette?
I found that I had fewer chain jump-offs with a compact cassette 11-25 because I could run the chain pretty tight. But at the end of the day, I like a wider cassette 12-32 for more gear range. Just curious what you did that worked? - 2/24/11, 3:29 PM
- Unknown said...
As a mechanic in the Seattle area, I can say that anything x10 is a very poor choice for daily use, unless money is not an issue. In my experience, a 10sp chain lasts about 6 months here (commuting, not a weekends bike). I still haven't heard any convincing arguments as to why 10sp offers any practical advantage over conventional 8 or 9sp rear drives, aside from competitive riding. I am interested to hear what reasons people have for choosing 10sp at all?
I guess in the end, my big question is whether the pros outweigh the cons of 10sp. With cost being much higher, lifespan being much lower, who's benefits from 10sp? Consumers or manufacturers? Both? Should Shimano and SRAM move to 11sp? - 2/24/11, 4:04 PM
- Jesse said...
I don't run an official 1x set up...I just don't use the small or big ring, ever. In effect I'm using 1x7 since the two outer cogs cause rubbing on the still installed front derailleur. I ride a moderately modified Kona Smoke in Seattle and have been loving this set up so much, for 9 months or so now, that I'm planning on removing the front derailleur and converting to a real 1x9 system some time this spring.
- Kevin Mulcahy said...
I use a 1x6 on my city-bike, which I'll also take on flat rides up to 100 miles. I use a 47 x 14-28
I occupy the empty half of the shifter braze-on with my VO Bell. :)
Chris: you say that you stay in the big ring 90% of the time. Does that mean you'll have to walk up a few of those hills? - 2/24/11, 4:32 PM
- latron said...
I have two 1x7s and they've been just fine in Boston (fairly flat, going around hills when needed). Am about to build up a 1x8, but will leave it at that -- 1x9, etc. seems too fussy, plus the cost of chains jumps once you go beyond 8 gears.
- Sean said...
Chain line?
I guess with narrower 10spd chains that's less of an issue compared with 8spd. - 2/24/11, 6:37 PM
- Doug in Seattle said...
I live in Seattle and am not skinny, so a 1x drive would not work for me.
I find the sweet spot for me is a 2x8, with the front being a 45x32 and the cassette being an 11x32. This is perfect for grinding up the huge hill I climb to work and for cruising around the countryside. My camping bike has a triple with a granny because I climb mountain passes s l o w l y.
I don't want to go higher than 8 speeds because the cost per chain and cassette goes up pretty quickly. I'm thinking of dropping back down to 7sp for my commuting bike just for the cost savings on those parts. - 2/24/11, 8:07 PM
- dwainedibbly said...
I have a never-ridden Vitus 929 frame that I'm eventually going to turn into a 1x9 using a 9 of 10 on 7 setup. (Don't want to force the bonded aluminum frame out to 130mm spacing.) I have some 10-speed DA bar ends that'll do nice, and a collection of other parts, some vintage, some V-O. It's going to be my "speedy city bike".
I used to race on the same kind of frame back in the 80s, so it's a flashback for me. - 2/24/11, 8:31 PM
- Unknown said...
I have run a 1x9 set up on a commuter for a few years, with many thousands of miles on the set up. Shifter is a Shimano bar-end and rear is 12-34. I've had no chain drop from bumps in the road, but occasionally when shifting in indexed mode. The chain drop more or less disappeared when I switched the shifter to friction. I noticed the indexed shifting would send a wave up the chain and sometimes launch it off the front ring. I use no inner guide; for bash guard I grinded down the outer ring on a bench grinder, then filed and sanded. That took about 15 minutes total, looks cool, and was free.
Like others I don't think there is too much performance benefit of the 1x set up. I did it just to make for less visual clutter on a city bike where I didn't need additional range. In my opinion this is not suggested for anything other than a city bike. If you're a racer or tourer and worried about weight you'd be better served with a downtube shifter and lightweight front derailler. These hardly weigh anything (esp compared to the bashguard and inner guide sported by the xc racers), and at some point the second ring will be handy.
One cost benefit of the 1x setup is that you can buy a set of bar-end or downtube shifters and get two bikes worth out it - if the front shifter runs friction you can run it to the rear mech. - 2/24/11, 9:48 PM
- Justin said...
I'm currently building up a city bike for a friend around a late 70s Motobecane mixte. I'm using a 44t up front and a 14-34 Suntour freewheel. I wasn't planning on using any sort of chain keeper. There are several nice VO bits on there. Do I get half credit for a 1x5?
- Uncle Ankle said...
I've run 1x7 (44x11/30) on a city bike in moderately hilly terrain, worked fine. It seemed one could, depending on chainline, choose whether to drop the chain inwards or outwards. I settled on inwards and fashioned a "dog's tooth" from a broken tail light bracket.
Single speed/Track/DH chainring makes a difference, too.
Once I decided to go touring on that bike, however, I added a 28t granny; shifted with my heel. - 2/25/11, 10:03 AM
- Steve said...
I have no personal experience with a 1x drivetrain, but history suggests there could be issues with dropping the chain. I've read accounts of AM-7 (1x7 drivetrain) Moultons that had such a tendency to drop the chain owners referred to them as "agents of the Devil" and "The Antichrist" (a nod to _The Gods Must Be Crazy_); and a chain keeper was devised for the AM Moulton. The easy solution is to use an old front derailleur locked in place as a chain keeper -- but that inevitably leads to the thought, if you're going to use a front derailleur anyway, why not just put on that second chain ring...?
- @realjanmaaso said...
I have both a 1x9 and a 2x8 where I never use the small ring. No problems at all.
With a proper length chain, I never ever drop the chain. - 2/25/11, 11:42 AM
- Mark said...
My commuter has a 1x8 drivetrain - the rder is controlled by a bar-end friction shifter. To keep the chain happy on the chainring, I have rigged a system with two chainguards, one on either side of the chainring. Works well. Had to fiddle a bit to work out the correct BB spindle to get a good chainline, but it works great. The Rder is a 'Deore' MTB rder.
- philcycles said...
Speaking off the top of my head-ie: no experience whatever-I'd sit down and figure out what gears I actually use. For me its about 6 or 7 and if I could get them with a 1x setup I might try it. I'd be wary about chainline issues and chain issues with a 1x10 but I believe a 1x7 might work for me. Perhaps I'll try it.
Phil Broen - 2/25/11, 12:18 PM
- Scott C said...
How do the variables in Sheldon Brown's Gear Calculator at:
figure into this topic? - 2/25/11, 1:04 PM
- Anonymous said...
I ride a 1 x 9 (12-25) with a 43 T chainring. The 43 x 25 combo is low enough to get me up just about anything though I mostly use the bike its on as my grocery getter. I do occasionally use it for longer rides and it's nice not to have to worry about front shifting. Another benefit iis not having a front derailleur, which enables you to use a chainguard (just put on a VO chainguard a month ago), which is nice.
- Joe said...
You should give the SRAM Apex a try, we've built a few rando style road bikes with it so far here at Sid's and although they've all had a compact double crank, personally I'd just set a bike up with a mid-sized single ring up front. The rear cassette gives you an almost MTB like gear range, with a mid-long cage derailleur, and depending how you set your bike up you could have a 1:1 gear ratio. Not to mention, SRAM is the cheaper, more affordable route to go (especially if you want to try out a new idea). I've done a 1x9 setup on a bike before with a 39 up front, and although there aren't too many giant hills near NYC, the gearing works out for pretty much everything so long as you're not trying to be speed racer in spandex! 10 speed gives you an even smoother jump between each gear.
- Steve A said...
Practically speaking, my Tricross operates as a 1X10 when on the road. The only time I use the small front cog on the road is to extend chain life when I have to go up steep, long hills with a headwind. I have not observed chain life to be unreasonably short. The bike has about 6000 miles and is just now on its second chain.
Set up properly, the chain has always stayed reliably on the front ring EXCEPT when running in really rough stuff, so if I wanted to cross race with 1X10, I'd add a guard up front. - 2/26/11, 9:53 AM
- Anonymous said...
I am in rural Brasil and ride 90% on dirt roads. I have a 1X8 on my all-rounder with 35 up front and a 11-34 mega-range on the back. I commute, tour and single-track with no problem. Paul's chain-keeper keeps my chain from launching.
- Robert Linthicum said...
What Mike said, from a Citroën-o-phile. Bought a Xsara Picasso for my wife. It's our family vehicle (my daily car is a bicycle) and it is frankly amazing value for money. Pity there's not a dealer network in The States.
- masmojo said...
As someone whose run Internally geared hubs most of my life, Single speeds and is currntly building a 1 X 8 get round town bike; I am kind of in the same boat. Some thoughts, using the bikes you are riding now you can experiment. While riding your current bike figure out which gear you ride in the most, that should help you determine where to start as far as gearing goes, then figure out what is the lowest gear you actually NEED! Lastly and here's the hard part; what is the highest gear you can fit and still live with! As you have already mentioned, much of this can very depending on where you are geographically. I live in Dallas which is relatively flat so I am opting for a fairly close ratio 8 speed cassette in the back and will fine tune the front ring to suit, in a hilly area I would probably choose the opposite Tactic.
Regarding dropping the chain; the Paul's chain thingy is good and bash guards are as well, but another option is to just take an old front derailer and run the limiting screws all the way in so that there is no adjustability to it. This might require a run to the hardware store for a longer screw or two, but no biggie! - 2/27/11, 9:45 AM
- Greg Priddy said...
I didn't realize there were so many fellow '1 x' practitioners. How exciting!
I happened into a 1 x 9 setup when the return spring on my triple FD failed. I rode the bike in the middle ring for a few weeks and decided the other other gears weren't all that necessary.
My current setup is a straight tooth Rocket Ring (42T) + bash guard in front. In the rear is an 11-32 Shimano cassette with a 34T in place of the 32T.
No issues with chain dropping, and the shift from the 28T to the 34T is reliable. I get up all the hills I want to on this rather heavy bike. - 2/27/11, 11:32 AM
- Anonymous said...
I use a single front on one of my bikes with a 5 or 6 freewheel in back and single Simplex lever. Works great. I used to be plagued with chain-dropping . . . First of all, make sure you're not trying to use a chainring with any sort of ramps and pins. Those are real good for shifting the chain off the ring. Get a nice clean round ring--not too skinny either. The chainring needs to line up in the middle of the freewheel. Finally, chain tension depends on the type of derailleur, and the right chain length matters. My experience is dropping the chain on a regular basis doesn't necessarily mean you need to add a chain keeper, but that the bike is basically out of tune in one of the ways above.
mw - 2/28/11, 7:32 PM
- Unknown said...
I have a 105 10-speed cassette and a 41T ring with bar-end shifters. Initially, a lot of folks were curious as to why I went with a single crank instead of a double. I do all of my riding in a city with a few hills and bridges, and the 1x10 is perfect for that. The only problem I have is with the non-indexed shifting - sometimes it's hard to get to the highest/lowest gears.
- fixedweasel said...
I'm kind of an odd bird I guess. I pretty much ride fixed for everything and leave the gears alone (but I'm building up a geared road bike right now). Mind, it is fairly flat where I live. I do all my commuting (44x17)/training (51x16 & 52x13)/racing (50x14)/centuries and even 200k Brevets (51x16) fixed with some mild climbing 3k'. I can easily see the 1x trend growing though, especially in areas that are tame. I've ridden with roadies that haven't even shifted once on a ride. And just to note with the chainguards. The reason cyclocross folks use 'em is because of the constant shifting over bumpy terrain. If one is riding on relatively smooth roads, you can probably get away w/o an inner/outer guard especially if you runnin' a long cage.
- Patrick said...
Funny, I just finished building a 1x9 (with a VO stem + 1" quill to threadless adapter) the other day as a beater/grocery-getter in town. I've been running 12-23 in back and 42 up front; the decision came because the middle ring on my road triple is 42, and I rarely found myself wanting to go to anything else. I keep a light Salsa guard on the outside and an N-Gear Jump Stop on the inside for security.
Seems to be working fine for now -- the chainline just looks awry at its farthest reaches, but I hardly need those gears anyway. Cost-benefit? Meh. I may have saved a little time/money/effort compared to buying a front derailleur and other rings and installing it all, but an anonymous commenter got it mostly right:
"It's one thing for racers who have decided they simply don't want or need to shift in the front, but for a recreational bike building it up turns into an exercise in elaborate minimalism. You end up buying some combination of a chainguard ring, an inboard chain guide, a new chainring, a shifter you don't end up using, and maybe even some extra brake levers. ... When the smoke clears on these builds it just ends up being a ton of work and parts without any real benefit."
Not that I'm not proud of it. - 3/10/11, 10:23 PM
- Andy said...
I am way late on this, but I had to post my experience. I have been running a 1x10 setup on a Polyvalent for about a year. I'm using an alloy rival right brifter, an alloy left SRAM brake lever that matches perfectly, and a SRAM Apex rear derailleur. I picked the Apex because it can handle an 11-32 cassette, but I've been happy with an 11-28 cassette so a short cage SRAM road derailleur would have been fine. I run a 39t front ring, and this gear combo works great for me in hilly Seattle with Hetre tires. I don't often carry more than 30lb on the front rack.
This setup works extremely well, and allows me to run a VO full-length alloy chainguard (the 44t version), which works excellent. I love never having to roll up my pants or worry about which pants I am wearing. My interest in knickers has faded considerably!
The only changes I've made to this setup over time are to add a bbg outer ring to keep the chain from going off the outside, which fits in the same spot as the 53t would normally on these road cranks, and an n-gear jump stop to keep the chain on from the in side. I very rarely dropped a chain even without these, but now I never do.
Andy - 11/9/11, 6:52 PM


text:
Madam Speaker, I join my colleagues in strong support of House Resolution 558, welcoming the accession of Bulgaria, Estonia, Latvia, Lithuania, Romania, Slovakia, and Slovenia to the North Atlantic Treaty Organization.
During my tenure in Congress, I have had considerable interaction with the leaders of these countries, as well as the opportunity to witness the transitions which have occurred. For several of our new NATO allies I first encountered as one-party communist states, as Warsaw Pact adversaries and as "captive nations." As Chairman of the Helsinki Commission, I have closely monitored their human rights performance and encouraged their democratic development. The transition for some has been particularly difficult, particularly with the effects of regional conflicts, political or economic crises. Throughout, their peoples have been our friends. Now, they become our allies.
While we must congratulate these countries, first and foremost, on the progress which brought them to this historic point, we can also take some credit for the investments we decided to make, through the human resources and bilateral assistance which planted the democratic ideals that now have triumphed. In my view, the returns on those investments have been notable.
In addition to these seven new NATO members, the resolution before the House also encourages the three members of the Adriatic Charter to continue their efforts toward eventual NATO membership. I particularly want to comment on Croatia. That country has had a particular challenge since 1990. As Yugoslavia fell apart and Croatia asserted its independence, the country faced not only the challenges of democratic transition but of surviving the Yugoslav conflict. From 1991 to 1995, significant portions of the country were destroyed or occupied. The conflict in neighboring Bosnia led to massive inflows of refugees. Croatia itself was vulnerable to those leaders with highly nationalist and less than democratic instincts.
While all of this slowed their transition, Croatia has rapidly moved–especially since 2000–to meet their democratic potential. In the last elections, a smooth transition in government took place, and we have a bilateral relationship which continues to strengthen over time. In addition, Croatia has become a key contributor to stability in a part of Europe where stability is highly fragile.
It is my hope, Madam Speaker, that we recognize this progress as Croatia seeks membership in NATO. Once Croatia meets the criteria for membership, the invitation to join should be extended. I would hope that the upcoming Istanbul summit will make this clear and mandate an assessment of Croatia's progress in this regard. It would be wrong and counter to U.S. interests to leave Croatia or any other country otherwise qualifying for NATO membership waiting unnecessarily.
I believe that taking this action would also encourage its Adriatic Charter partners, Albania and Macedonia, in meeting the criteria for membership more quickly. Rather than abandon its partners, Croatia will help them make progress as well. Albania and Macedonia are also good friends of the United States and would benefit from this encouragement. Ultimately, Bosnia and Herzegovina and Serbia and Montenegro would benefit as well, all in the interest of European security and, therefore, U.S. security interests.

subset: commoncrawl


text:
Eskragh, Northern Ireland's Premier Full Stack Web Development Partner
Enhance your online visibility and drive organic traffic with Mourne Connect's strategic, results-driven Full Stack Web Development.
Expert Full Stack Web Development in Eskragh, Northern Ireland
At Mourne Connect, we provide bespoke Full Stack Web Development that drives engagement and accelerates growth for your business
Searching for the best Full Stack Web Development in Eskragh, Northern Ireland?
Look no further than Mourne Connect, your trusted partner in digital transformation.
For years, the Mourne Connect team have been pioneering digital solutions in a myriad of sectors. Our skilled team of professionals thrive on delivering high-quality Full Stack Web Development for businesses across Eskragh, Northern Ireland and afar. Our services are tailored to fit your unique needs. Whether you're a fledgling start-up or a long-standing corporation, our services are designed to catapult your business towards growth and success.
With Mourne Connect, you're not just choosing a provider for Full Stack Web Development – you're choosing a partner who cares about your business as much as you do. We delve deep into understanding your needs, vision, and values. This way, our Full Stack Web Development doesn't just meet your expectations; it surpasses them, giving your business an edge over competitors in Eskragh, Northern Ireland and beyond!
What sets our Full Stack Web Development apart is our commitment to quality, our innovative approach, and our customer-centric processes. We are constantly exploring new technologies and techniques to ensure our services remain top-tier. No matter how diverse or specific your Full Stack Web Development needs are, we're equipped to handle them with skill, precision, and a passion for excellence.
Our dedicated team in Eskragh, Northern Ireland works tirelessly to ensure your goals are not just achieved but exceeded. With Mourne Connect's Full Stack Web Development, you can expect increased efficiency, improved visibility, and ultimately, enhanced profitability.
Ready to transform your business operations with our premier Full Stack Web Development?
Let's start the journey towards success together.
Get in touch today and experience the Mourne Connect difference.


text:
Talk about adding insult to injury thats exactly what last Thursdays monster storm did to Karing by Kristina on Mount Vernon Avenue in Del Ray.
Not only was the boutique pet shop without power until Saturday night, but it was also burglarized Friday night because the loss of power also killed the alarm system.
They came in and cleaned out our cash register, said owner Kristina Robertson. We discovered it when we opened up late Saturday.
As was the case in many areas, the loss and regaining of electric power seemed to be highly erratic.
Just two blocks down Mount Vernon Avenue, Kiskadee regained their power by Friday morning, according to Cornelia Hall, co-owner. There was no damage. We really lucked out, Hall said.
The West End seemed to fare very well with owners reporting little or no business disruption.
There was no problem at all, said Christopher St. Pierre, owner of Authentically Amish in the Foxchase Shopping Center on Duke Street. Our entire shopping center seemed to fare very well.
That was also the case for Tempo Restaurant at 4231 Duke St.
We werent interrupted at all, said manager Cesar Lazo. It was a very busy night for us with a lot of walk-in business.
In Old Town it was a mixed bag with businesses reporting everything from total power loss to only partial or no loss. Pat Troys Irelands Own had some loss of power but they were able to remain open.
We were very busy Thursday night, said Kathleen Molloy, the restaurants manager. The only problem was we had to do credit card payments the old fashioned way because the machine was down. And, it seemed like everyone was paying by credit card.
However, the story was very different at Fontaine Caffe&Creperie around the corner on South Royal Street. We had to close because we were totally out of power until after 11 p.m., said Eren Leon.
Lower King Street and Union Street faced a similar predicament. We were out about four hours, said Bart Paz, manager of Bugsys Pizza Restaurant & Sports Bar. We closed when the storm hit and didnt open until Friday morning.
The Fish Market was also forced to close when the storm hit and wasnt able to open until the next day, according to manager Jesse Mass. Thankfully for the restaurant, the worst case scenario didnt materialize.
We didnt have any spoilage. The freezers were closed and everything was okay, Mass said.
The Christmas Attic on Union Street was forced to close when they lost power about 5 p.m., according to Fay Carter, the stores owner, but business really boomed over the weekend. The heat didnt seem to bother any of our customers, she said.
That was not the case at Kings Jewelry, mid-way up King Street, where owner Norman Bradford said the power was out until about 2 p.m. on Saturday.
We were open and had customers but it was miserable in here, Bradford said. I know I lost one significant sale because our polishing machinery wouldnt operate. People seem to forget that there was a time when there was no such thing as air conditioning.
Like so many things in life, it all depended on where you were when the storm blew in. Mother Nature doesnt play favorites or does she?


text:
The authorized biography of the creator of Middle-earth. In the decades since his death in September 1973, millions have read THE HOBBIT, THE LORD OF THE RINGS, and THE SILMARILLION and become fascinated about the very private man behind the books. Born in South Africa in January 1892, John Ronald Reuel Tolkien was orphaned in childhood and brought up in near-poverty. He served in the first World War, surviving the Battle of the Somme, where he lost many of the closest friends he'd ever had. After the war he returned to the academic life, achieving high repute as a scholar and university teacher, eventually becoming Merton Professor of English at Oxford where he was a close friend of C.S. Lewis and the other writers known as The Inklings.
Then suddenly his life changed dramatically. One day while grading essay papers he found himself writing 'In a hole in the ground there lived a hobbit' - and worldwide renown awaited him.
Humphrey Carpenter was given unrestricted access to all Tolkien's papers, and interviewed his friends and family. From these sources he follows the long and painful process of creation that produced THE LORD OF THE RINGS and THE SILMARILLION and offers a wealth of information about the life and work of the twentieth century's most cherished author.


text:
PostgreSQL 8.2.6 Documentation | ||||
Prev | Fast Backward | Appendix E. Release Notes | Fast Forward | Next |
Release date: 2006-12-05
This release adds many functionality and performance improvements that were requested by users, including:
Query language enhancements including INSERT/UPDATE/DELETE RETURNING , multirow VALUES lists, and optional target-table alias in UPDATE / DELETE
Index creation without blocking concurrent INSERT / UPDATE / DELETE operations
Many query optimization improvements, including support for reordering outer joins
Improved sorting performance with lower memory usage
More efficient locking with better concurrency
More efficient vacuuming
Easier administration of warm standby servers
New FILLFACTOR support for tables and indexes
Monitoring, logging, and performance tuning additions
More control over creating and dropping objects
Table inheritance relationships can be defined for and removed from pre-existing tables
COPY TO can copy the output of an arbitrary SELECT statement
Array improvements, including nulls in arrays
Aggregate-function improvements, including multiple-input aggregates and SQL:2003 statistical functions
Many contrib/ improvements
A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.
Observe the following incompatibilities:
Set escape_string_warning to on by default (Bruce)
This issues a warning if backslash escapes are used in non-escape (non- E'' ) strings .
Change the row constructor syntax ( ROW(...) ) so that list elements foo.* will be expanded to a list of their member fields, rather than creating a nested row type field as formerly (Tom)
The new behavior is substantially more useful since it allows, for example, triggers to check for data changes with IF row(new.*) IS DISTINCT FROM row(old.*) . The old behavior is still available by omitting .* .
Make row comparisons follow SQL standard semantics and allow them to be used in index scans (Tom)
Previously, row = and <> comparisons followed the standard but < <= > >= did not. A row comparison can now be used as an index constraint for a multicolumn index matching the row value.
Make row IS [ NOT ] NULL tests follow SQL standard semantics (Tom)
The former behavior conformed to the standard for simple cases with IS NULL , but IS NOT NULL would return true if any row field was non-null, whereas the standard says it should return true only when all fields are non-null.
Make SET CONSTRAINT affect only one constraint (Kris Jurka)
In previous releases, SET CONSTRAINT modified all constraints with a matching name. In this release, the schema search path is used to modify only the first matching constraint. A schema specification is also supported. This more nearly conforms to the SQL standard.
Remove RULE permission for tables, for security reasons (Tom)
As of this release, only a table's owner can create or modify rules for the table. For backwards compatibility, GRANT / REVOKE RULE is still accepted, but it does nothing.
Array comparison improvements (Tom)
Now array dimensions are also compared.
Change array concatenation to match documented behavior (Tom)
This changes the previous behavior where concatenation would modify the array lower bound.
Make command-line options of postmaster and postgres identical (Peter)
This allows the postmaster to pass arguments to each backend without using -o . Note that some options are now only available as long-form options, because there were conflicting single-letter options.
Deprecate use of postmaster symbolic link (Peter)
postmaster and postgres commands now act identically, with the behavior determined by command-line options. The postmaster symbolic link is kept for compatibility, but is not really needed.
Change log_duration to output even if the query is not output (Tom)
In prior releases, log_duration only printed if the query appeared earlier in the log.
as 12-hour intervals
Most applications should use HH24 unless they want a 12-hour display.
Zero unmasked bits in conversion from INET to CIDR (Tom)
This ensures that the converted value is actually valid for CIDR .
Remove australian_timezones configuration variable (Joachim Wieland)
This variable has been superseded by a more general facility for configuring timezone abbreviations.
Improve cost estimation for nested-loop index scans (Tom)
This might eliminate the need to set unrealistically small values of random_page_cost . If you have been using a very small random_page_cost , please recheck your test cases.
Change behavior of pg_dump -n and -t options. (Greg Sabino Mullane)
See the pg_dump manual page for details.
to return a useful value (Martijn van Oosterhout)
as returning
void *
, rather than
(Martijn van Oosterhout)
This allows applications to use the function without including the OpenSSL headers.
C-language loadable modules must now include a PG_MODULE_MAGIC macro call for version compatibility checking (Martijn van Oosterhout)
For security's sake, modules used by a PL/PerlU function are no longer available to PL/Perl functions (Andrew)
Note: This also implies that data can no longer be shared between a PL/Perl function and a PL/PerlU function. Some Perl installations have not been compiled with the correct flags to allow multiple interpreters to exist within a single process. In this situation PL/Perl and PL/PerlU cannot both be used in a single backend. The solution is to get a Perl installation which supports multiple interpreters.
, rename
will remain for backward compatibility, but its behavior will change to do schema checking in a future release.
Remove contrib/ora2pg/ , now at http://www.samse.fr/GPL/ora2pg
Remove contrib modules that have been migrated to PgFoundry: adddepend , dbase , dbmirror , fulltextindex , mac , userlock
Remove abandoned contrib modules: mSQL-interface , tips
Remove QNX and BEOS ports (Bruce)
These ports no longer had active maintainers.
Below you will find a detailed account of the changes between PostgreSQL 8.2 and the previous major release.
Allow the planner to reorder outer joins in some circumstances (Tom)
In previous releases, outer joins would always be evaluated in the order written in the query. This change allows the query optimizer to consider reordering outer joins, in cases where it can determine that the join order can be changed without altering the meaning of the query. This can make a considerable performance difference for queries involving multiple outer joins or mixed inner and outer joins.
Improve efficiency of IN (list-of-expressions) clauses (Tom)
Improve sorting speed and reduce memory usage (Simon, Tom)
Improve subtransaction performance (Alvaro, Itagaki Takahiro, Tom)
Add FILLFACTOR to table and index creation (ITAGAKI Takahiro)
This leaves extra free space in each table or index page, allowing improved performance as the database grows. This is particularly valuable to maintain clustering.
Increase default values for shared_buffers and max_fsm_pages (Andrew)
Improve locking performance by breaking the lock manager tables into sections (Tom)
This allows locking to be more fine-grained, reducing contention.
Reduce locking requirements of sequential scans (Qingqing Zhou)
Reduce locking required for database creation and destruction (Tom)
Improve the optimizer's selectivity estimates for LIKE , ILIKE , and regular expression operations (Tom)
Improve planning of joins to inherited tables and UNION ALL views (Tom)
Allow constraint exclusion to be applied to inherited UPDATE and DELETE queries (Tom)
SELECT already honored constraint exclusion.
Improve planning of constant WHERE clauses, such as a condition that depends only on variables inherited from an outer query level (Tom)
Protocol-level unnamed prepared statements are re-planned for each set of BIND values (Tom)
This improves performance because the exact parameter values can be used in the plan.
Speed up vacuuming of B-Tree indexes (Heikki Linnakangas, Tom)
Avoid extra scan of tables without indexes during VACUUM (Greg Stark)
Improve multicolumn GiST indexing (Oleg, Teodor)
Remove dead index entries before B-Tree page split (Junji Teramoto)
Allow a forced switch to a new transaction log file (Simon, Tom)
This is valuable for keeping warm standby slave servers in sync with the master. Transaction log file switching now also happens automatically during
. This ensures that all transaction log files needed for recovery can be archived immediately.
Add WAL informational functions (Simon)
Add functions for interrogating the current transaction log insertion point and determining
filenames from the hex
locations displayed by
and related functions.
Improve recovery from a crash during WAL replay (Simon)
The server now does periodic checkpoints during WAL recovery, so if there is a crash, future WAL recovery is shortened. This also eliminates the need for warm standby servers to replay the entire log since the base backup if they crash.
Improve reliability of long-term WAL replay (Heikki, Simon, Tom)
Formerly, trying to roll forward through more than 2 billion transactions would not work due to XID wraparound. This meant warm standby servers had to be reloaded from fresh base backups periodically.
Add archive_timeout to force transaction log file switches at a given interval (Simon)
This enforces a maximum replication delay for warm standby servers.
Add native LDAP authentication (Magnus Hagander)
This is particularly useful for platforms that do not support PAM , such as Windows.
Add GRANT CONNECT ON DATABASE (Gevik Babakhani)
This gives SQL-level control over database access. It works as an additional filter on top of the existing pg_hba.conf controls.
Add support for SSL Certificate Revocation List ( CRL ) files (Libor Hohoš)
The server and libpq both recognize CRL files now.
GiST indexes are now clusterable (Teodor)
Remove routine autovacuum server log entries (Bruce)
pg_stat_activity now shows autovacuum activity.
Track maximum XID age within individual tables, instead of whole databases (Alvaro)
This reduces the overhead involved in preventing transaction ID wraparound, by avoiding unnecessary VACUUMs.
Add last vacuum and analyze timestamp columns to the stats collector (Larry Rosenman)
These values now appear in the pg_stat_*_tables system views.
Improve performance of statistics monitoring, especially stats_command_string (Tom, Bruce)
This release enables stats_command_string by default, now that its overhead is minimal. This means pg_stat_activity will now show all active queries by default.
Add a waiting column to pg_stat_activity (Tom)
This allows pg_stat_activity to show all the information included in the ps display.
Add configuration parameter update_process_title to control whether the ps display is updated for every command (Bruce)
On platforms where it is expensive to update the ps display, it might be worthwhile to turn this off and rely solely on pg_stat_activity for status information.
Allow units to be specified in configuration settings (Peter)
For example, you can now set shared_buffers to 32MB rather than mentally converting sizes.
Add support for include directives in postgresql.conf (Joachim Wieland)
Improve logging of protocol-level prepare/bind/execute messages (Bruce, Tom)
Such logging now shows statement names, bind parameter values, and the text of the query being executed. Also, the query text is properly included in logged error messages when enabled by log_min_error_statement .
Prevent max_stack_depth from being set to unsafe values
On platforms where we can determine the actual kernel stack depth limit (which is most), make sure that the initial default value of max_stack_depth is safe, and reject attempts to set it to unsafely large values.
Enable highlighting of error location in query in more cases (Tom)
The server is now able to report a specific error location for some semantic errors (such as unrecognized column name), rather than just for basic syntax errors as before.
Fix "failed to re-find parent key" errors in VACUUM (Tom)
Clean out pg_internal.init cache files during server restart (Simon)
This avoids a hazard that the cache files might contain stale data after PITR recovery.
Fix race condition for truncation of a large relation across a gigabyte boundary by VACUUM (Tom)
Fix bug causing needless deadlock errors on row-level locks (Tom)
Fix bugs affecting multi-gigabyte hash indexes (Tom)
Each backend process is now its own process group leader (Tom)
This allows query cancel to abort subprocesses invoked from a backend or archive/recovery process.
Add INSERT / UPDATE / DELETE RETURNING (Jonah Harris, Tom)
This allows these commands to return values, such as the computed serial key for a new row. In the UPDATE case, values from the updated version of the row are returned.
Add support for multiple-row VALUES clauses, per SQL standard (Joe, Tom)
This allows INSERT to insert multiple rows of constants, or queries to generate result sets using constants. For example, INSERT ... VALUES (...), (...), .... , and SELECT * FROM (VALUES (...), (...), ....) AS alias(f1, ...) .
Allow UPDATE and DELETE to use an alias for the target table (Atsushi Ogawa)
The SQL standard does not permit an alias in these commands, but many database systems allow one anyway for notational convenience.
Allow UPDATE to set multiple columns with a list of values (Susanne Ebrecht)
This is basically a short-hand for assigning the columns and values in pairs. The syntax is UPDATE tab SET ( column , ...) = ( val , ...) .
Make row comparisons work per standard (Tom)
The forms <, <=, >, >= now compare rows lexicographically, that is, compare the first elements, if equal compare the second elements, and so on. Formerly they expanded to an AND condition across all the elements, which was neither standard nor very useful.
Add CASCADE option to TRUNCATE (Joachim Wieland)
This causes TRUNCATE to automatically include all tables that reference the specified table(s) via foreign keys. While convenient, this is a dangerous tool — use with caution!
Support FOR UPDATE and FOR SHARE in the same SELECT command (Tom)
Add IS NOT DISTINCT FROM (Pavel Stehule)
This operator is similar to equality ( = ), but evaluates to true when both left and right operands are NULL , and to false when just one is, rather than yielding NULL in these cases.
Improve the length output used by UNION / INTERSECT / EXCEPT (Tom)
When all corresponding columns are of the same defined length, that length is used for the result, rather than a generic length.
Allow ILIKE to work for multi-byte encodings (Tom)
now calls
and then uses
. Locale-specific regular expression patterns still do not work in these encodings.
Enable standard_conforming_strings to be turned on (Kevin Grittner)
This allows backslash escaping in strings to be disabled, making PostgreSQL more standards-compliant. The default is off for backwards compatibility, but future releases will default this to on .
Do not flatten subqueries that contain volatile functions in their target lists (Jaime Casanova)
This prevents surprising behavior due to multiple evaluation of a
function (such as
). It might cause performance degradation in the presence of functions that are unnecessarily marked as
Add system views pg_prepared_statements and pg_cursors to show prepared statements and open cursors (Joachim Wieland, Neil)
These are very useful in pooled connection setups.
Support portal parameters in EXPLAIN and EXECUTE (Tom)
This allows, for example, JDBC ? parameters to work in these commands.
If SQL -level PREPARE parameters are unspecified, infer their types from the content of the query (Neil)
Protocol-level PREPARE already did this.
Allow LIMIT and OFFSET to exceed two billion (Dhanaraj M)
Add TABLESPACE clause to CREATE TABLE AS (Neil)
This allows a tablespace to be specified for the new table.
Add ON COMMIT clause to CREATE TABLE AS (Neil)
This allows temporary tables to be truncated or dropped on transaction commit. The default behavior is for the table to remain until the session ends.
Add INCLUDING CONSTRAINTS to CREATE TABLE LIKE (Greg Stark)
This allows easy copying of CHECK constraints to a new table.
Allow the creation of placeholder (shell) types (Martijn van Oosterhout)
A shell type declaration creates a type name, without specifying any of the details of the type. Making a shell type is useful because it allows cleaner declaration of the type's input/output functions, which must exist before the type can be defined "for real" . The syntax is CREATE TYPE typename .
Aggregate functions now support multiple input parameters (Sergey Koposov, Tom)
Add new aggregate creation syntax (Tom)
The new syntax is CREATE AGGREGATE aggname ( input_type ) ( parameter_list ) . This more naturally supports the new multi-parameter aggregate functionality. The previous syntax is still supported.
Add ALTER ROLE PASSWORD NULL to remove a previously set role password (Peter)
Add DROP object IF EXISTS for many object types (Andrew)
This allows DROP operations on non-existent objects without generating an error.
Add DROP OWNED to drop all objects owned by a role (Alvaro)
Add REASSIGN OWNED to reassign ownership of all objects owned by a role (Alvaro)
This, and DROP OWNED above, facilitate dropping roles.
Add GRANT ON SEQUENCE syntax (Bruce)
This was added for setting sequence-specific permissions. GRANT ON TABLE for sequences is still supported for backward compatibility.
permission for sequences that allows only
, not
permission allows more fine-grained control over sequence access. Granting
allows users to increment a sequence, but prevents them from setting the sequence to an arbitrary value using
Add ALTER TABLE [ NO ] INHERIT (Greg Stark)
This allows inheritance to be adjusted dynamically, rather than just at table creation and destruction. This is very valuable when using inheritance to implement table partitioning.
Allow comments on global objects to be stored globally (Kris Jurka)
Previously, comments attached to databases were stored in individual databases, making them ineffective, and there was no provision at all for comments on roles or tablespaces. This change adds a new shared catalog pg_shdescription and stores comments on databases, roles, and tablespaces therein.
Add option to allow indexes to be created without blocking concurrent writes to the table (Greg Stark, Tom)
The new syntax is CREATE INDEX CONCURRENTLY . The default behavior is still to block table modification while a index is being created.
Provide advisory locking functionality (Abhijit Menon-Sen, Tom)
This is a new locking API designed to replace what used to be in /contrib/userlock. The userlock code is now on pgfoundry.
Allow COPY to dump a SELECT query (Zoltan Boszormenyi, Karel Zak)
This allows COPY to dump arbitrary SQL queries. The syntax is COPY (SELECT ...) TO .
Make the COPY command return a command tag that includes the number of rows copied (Volkan YAZICI)
Allow VACUUM to expire rows without being affected by other concurrent VACUUM operations (Hannu Krossing, Alvaro, Tom)
Make initdb detect the operating system locale and set the default DateStyle accordingly (Peter)
This makes it more likely that the installed postgresql.conf DateStyle value will be as desired.
Reduce number of progress messages displayed by initdb (Tom)
Allow full timezone names in timestamp input values (Joachim Wieland)
For example, '2006-05-24 21:11 America/New_York'::timestamptz .
Support configurable timezone abbreviations (Joachim Wieland)
A desired set of timezone abbreviations can be chosen via the configuration parameter timezone_abbreviations .
Add pg_timezone_abbrevs and pg_timezone_names views to show supported timezones (Magnus Hagander)
, and
is the current wall-clock time,
is the time the current statement arrived at the server, and
is an alias for
to print localized month and day names (Euler Taveira de Oliveira)
to output
specifications (Bruce)
Intervals and times are treated as 24-hour periods, e.g. 25 hours is considered AM .
Add new function
to adjust interval units (Mark Dilger)
Allow timezone offsets up to 14:59 away from GMT
Kiribati uses GMT+14, so we'd better accept that.
Interval computation improvements (Michael Glaesemann, Bruce)
Allow arrays to contain NULL elements (Tom)
Allow assignment to array elements not contiguous with the existing entries (Tom)
The intervening array positions will be filled with nulls. This is per SQL standard.
New built-in operators for array-subset comparisons ( @> , <@ , && ) (Teodor, Tom)
These operators can be indexed for many data types using GiST or GIN indexes.
Add convenient arithmetic operations on INET / CIDR values (Stephen R. van den Berg)
The new operators are & (and), | (or), ~ (not), inet + int8 , inet - int8 , and inet - inet .
Add new aggregate functions from SQL:2003 (Neil)
The new functions are
, and
are merely renamings of the existing aggregates
. The latter names remain available for backward compatibility.
Add SQL:2003 statistical aggregates (Sergey Koposov)
New functions:
Allow domains to be based on other domains (Tom)
Properly enforce domain CHECK constraints everywhere (Neil, Tom)
For example, the result of a user-defined function that is declared to return a domain type is now checked against the domain's constraints. This closes a significant hole in the domain implementation.
Fix problems with dumping renamed SERIAL columns (Tom)
The fix is to dump a SERIAL column by explicitly specifying its DEFAULT and sequence elements, and reconstructing the SERIAL column on reload using a new ALTER SEQUENCE OWNED BY command. This also allows dropping a SERIAL column specification.
Add a server-side sleep function
(Joachim Wieland)
Add all comparison operators for the tid (tuple id) data type (Mark Kirkwood, Greg Stark, Tom)
Add TG_table_name and TG_table_schema to trigger parameters (Andrew)
TG_relname is now deprecated. Comparable changes have been made in the trigger parameters for the other PLs as well.
Allow FOR statements to return values to scalars as well as records and row types (Pavel Stehule)
Add a BY clause to the FOR loop, to control the iteration increment (Jaime Casanova)
Add STRICT to SELECT INTO (Matt Miller)
STRICT mode throws an exception if more or less than one row is returned by the SELECT , for Oracle PL/SQL compatibility.
Add table_name and table_schema to trigger parameters (Adam Sjøgren)
Add prepared queries (Dmitry Karasik)
Make $_TD trigger data a global variable (Andrew)
Previously, it was lexical, which caused unexpected sharing violations.
Run PL/Perl and PL/PerlU in separate interpreters, for security reasons (Andrew)
In consequence, they can no longer share data nor loaded modules. Also, if Perl has not been compiled with the requisite flags to allow multiple interpreters, only one of these languages can be used in any given backend process.
Named parameters are passed as ordinary variables, as well as in the args[] array (Sven Suursoho)
Add table_name and table_schema to trigger parameters (Andrew)
Allow returning of composite types and result sets (Sven Suursoho)
Return result-set as list , iterator , or generator (Sven Suursoho)
Allow functions to return void (Neil)
Python 2.5 is now supported (Tom)
Add new command \password for changing role password with client-side password encryption (Peter)
Allow \c to connect to a new host and port number (David, Volkan YAZICI)
Add tablespace display to \l+ (Philip Yarra)
Improve \df slash command to include the argument names and modes ( OUT or INOUT ) of the function (David Fetter)
Support binary COPY (Andreas Pflug)
Add option to run the entire session in a single transaction (Simon)
Use option -1 or --single-transaction .
Support for automatically retrieving SELECT results in batches using a cursor (Chris Mair)
This is enabled using \set FETCH_COUNT n . This feature allows large result sets to be retrieved in psql without attempting to buffer the entire result set in memory.
Make multi-line values align in the proper column (Martijn van Oosterhout)
Field values containing newlines are now displayed in a more readable fashion.
Save multi-line statements as a single entry, rather than one line at a time (Sergey E. Koposov)
This makes up-arrow recall of queries easier. (This is not available on Windows, because that platform uses the native command-line editing present in the operating system.)
Make the line counter 64-bit so it can handle files with more than two billion lines (David Fetter)
Report both the returned data and the command status tag for INSERT / UPDATE / DELETE RETURNING (Tom)
Allow complex selection of objects to be included or excluded by pg_dump (Greg Sabino Mullane)
pg_dump now supports multiple -n (schema) and -t (table) options, and adds -N and -T options to exclude objects. Also, the arguments of these switches can now be wild-card expressions rather than single object names, for example -t 'foo*' , and a schema can be part of a -t or -T switch, for example -t schema1.table1 .
Add pg_restore --no-data-for-failed-tables option to suppress loading data if table creation failed (i.e., the table already exists) (Martin Pitt)
Add pg_restore option to run the entire session in a single transaction (Simon)
Use option -1 or --single-transaction .
to encrypt passwords (Tom)
This allows passwords to be sent pre-encrypted for commands like ALTER ROLE ... PASSWORD .
Add function
This allows applications to query the thread-safety status of the library.
, and related functions to return information about previously prepared statements and open cursors (Volkan YAZICI)
Allow LDAP lookups from pg_service.conf (Laurenz Albe)
Allow a hostname in ~/.pgpass to match the default socket directory (Bruce)
A blank hostname continues to match any Unix-socket connection, but this addition allows entries that are specific to one of several postmasters on the machine.
Allow SHOW to put its result into a variable (Joachim Wieland)
Add COPY TO STDOUT (Joachim Wieland)
Add regression tests (Joachim Wieland, Michael)
Major source code cleanups (Joachim Wieland, Michael)
Allow MSVC to compile the PostgreSQL server (Magnus, Hiroshi Saito)
Add MSVC support for utility commands and pg_dump (Hiroshi Saito)
Add support for Windows code pages 1253 , 1254 , 1255 , and 1257 (Kris Jurka)
Drop privileges on startup, so that the server can be started from an administrative account (Magnus)
Stability fixes (Qingqing Zhou, Magnus)
Add native semaphore implementation (Qingqing Zhou)
The previous code mimicked SysV semaphores.
Add GIN (Generalized Inverted iNdex) index access method (Teodor, Oleg)
Remove R-tree indexing (Tom)
Rtree has been re-implemented using GiST . Among other differences, this means that rtree indexes now have support for crash recovery via write-ahead logging (WAL).
Reduce libraries needlessly linked into the backend (Martijn van Oosterhout, Tom)
Add a configure flag to allow libedit to be preferred over GNU readline (Bruce)
Use configure --with-libedit-preferred .
Allow installation into directories containing spaces (Peter)
Improve ability to relocate installation directories (Tom)
Add support for Solaris x86_64 using the Solaris compiler (Pierre Girard, Theo Schlossnagle, Bruce)
Add DTrace support (Robert Lor)
Add PG_VERSION_NUM for use by third-party applications wanting to test the backend version in C using > and < comparisons (Bruce)
Add XLOG_BLCKSZ as independent from BLCKSZ (Mark Wong)
Add LWLOCK_STATS define to report locking activity (Tom)
Emit warnings for unknown configure options (Martijn van Oosterhout)
Add server support for "plugin" libraries that can be used for add-on tasks such as debugging and performance measurement (Korry Douglas)
This consists of two features: a table of "rendezvous variables" that allows separately-loaded shared libraries to communicate, and a new configuration parameter local_preload_libraries that allows libraries to be loaded into specific sessions without explicit cooperation from the client application. This allows external add-ons to implement features such as a PL/PgSQL debugger.
Rename existing configuration parameter preload_libraries to shared_preload_libraries (Tom)
This was done for clarity in comparison to local_preload_libraries .
Add new configuration parameter server_version_num (Greg Sabino Mullane)
This is like server_version , but is an integer, e.g. 80200 . This allows applications to make version checks more easily.
Add a configuration parameter seq_page_cost (Tom)
Re-implement the regression test script as a C program (Magnus, Tom)
Allow loadable modules to allocate shared memory and lightweight locks (Marc Munro)
Add automatic initialization and finalization of dynamically loaded libraries (Ralf Engelschall, Tom)
are called if the library defines such symbols. Hence we no longer need to specify an initialization function in
; we can assume that the library used the
convention instead.
Add PG_MODULE_MAGIC header block to all shared object files (Martijn van Oosterhout)
The magic block prevents version mismatches between loadable object files and servers.
Add shared library support for AIX (Laurenz Albe)
New XML documentation section (Bruce)
Major tsearch2 improvements (Oleg, Teodor)
multibyte encoding support, including UTF8
query rewriting support
improved ranking functions
thesaurus dictionary support
Ispell dictionaries now recognize MySpell format, used by OpenOffice
GIN support
Add adminpack module containing Pgadmin administration functions (Dave)
These functions provide additional file system access routines not present in the default PostgreSQL server.
Add sslinfo module (Victor Wagner)
Reports information about the current connection's SSL certificate.
Add pgrowlocks module (Tatsuo)
This shows row locking information for a specified table.
Add hstore module (Oleg, Teodor)
Add isn module, replacing isbn_issn (Jeremy Kronuz)
This new implementation supports EAN13 , UPC , ISBN (books), ISMN (music), and ISSN (serials).
Add index information functions to pgstattuple (ITAGAKI Takahiro, Satoshi Nagayasu)
Add pg_freespacemap module to display free space map information (Mark Kirkwood)
pgcrypto now has all planned functionality (Marko Kreen)
Include iMath library in pgcrypto to have the public-key encryption functions always available.
Add SHA224 algorithm that was missing in OpenBSD code.
Activate builtin code for SHA224/256/384/512 hashes on older OpenSSL to have those algorithms always available.
New function gen_random_bytes() that returns cryptographically strong randomness. Useful for generating encryption keys.
Remove digest_exists(), hmac_exists() and cipher_exists() functions.
Improvements to cube module (Joshua Reich)
New functions are
cube(float[], float[])
, and
cube_subset(cube, int4[])
Add async query capability to dblink (Kai Londenberg, Joe Conway)
New operators for array-subset comparisons ( @> , <@ , && ) (Tom)
Various contrib packages already had these operators for their datatypes, but the naming wasn't consistent. We have now added consistently named array-subset comparison operators to the core code and all the contrib packages that have such functionality. (The old names remain available, but are deprecated.)
Add uninstall scripts for all contrib packages that have install scripts (David, Josh Drake)


text:
- Astrid Alauda
No time, running. How many of you people have said or heard that sentence before? Too many, unfortunately. Sadly, most of us regularly struggle with a life that is far from being relaxed and suffer from that situation.
We always seem to be rushing and stressing like crazy, because our days are not long enough and we are engrossed in work and in doing chores. We are not capable of coping with the fact that hours pass incredibly fast and that we rarely get anything done as expected. I don't know about you, but although I don't mind being busy and having lots of things to do, I hate being on the run or put under pressure. It is just not a Feng-Shui/Zen lifetsyle. As a matter of fact, it is not for no reason that my favorite expressions is "trrrrranquile!" (pronounced with a Spanish accent)...
I have no clue why suddenly time started to fly by with infinite velocity, but I remember that when I was a college girl I went to school from 8am 'til around 5pm, then I studied for a while, listened to some music/CD's, wrote letters to my penpals, read novels, roamed town with friends and even had leisure to get bored or lie on my bed daydreaming. Nowadays, I barely can do half of those things and I'm continually keeping a concentrated eye on the clock!
You see, as antagonistic as it may sound, despite being a messy and chaotic individual, I am also somebody who needs structure in life, who likes a certain routine and things to be square, otherwise I tend to feel insecure, stressed and panicky. Is it bad or is it good? I don't believe it is, yet I must admit that the motives of this behaviour pattern elude me. I'm pretty sure a psychologist would find a concrete explaination, but I know that's how things work for me. I profoundly dislike having a disorganized agenda. The only places where I like anarchy and clutter to reign supreme are in my computer room, my kitchen or in arts (painting, photography, cinema or music).
For example, if I can't blog as planned I become very fidgety and anxious. Some mornings, I wake up with my heart beating loudly and an unhealthy need to run out of bed in order to sit in front of the computer. Although blogging brings me joy and fulfills my soul, it can also be a burden and a heavy weight for a disciplined perfectionist like me who has high expectations and seldom values herself positively. I am constantly afraid of never being able to deliver quality articles/recipes that are cunning enough.
I really have to find a solution to this problem as my painstaking fussiness and hairsplitting manners can be a real hindrance to creativity and productivity. I should learn how to be a little more laidback and cool when it comes to my blog, otherwise I am likely to end up loathing that activity, loosing your mojo and ending up with a burn-out, and that is something I have come dangerously close to experiencing lately...
When what you like becomes a "punishment" that brings pain, tension and confusion, then it is a sign that you are doing it the wrong way. Such destructive feelings can completely eradicate all the pleasure you used to feel while exercising your hobby and disgust you to the point of no return. Bad and really not constructive, so don't forget not to take blogging too seriously and be casual!
Anayway, despite my hectic mood and difficulty to deal with my "overbooked" agenda, I have nonetheless been able to prepare a post to share with you. I might be someone who needs a lot of energy to get out of her slumber, but it is always a joy to kick myself in the ass for you, my dear readers! So, this Friday I am presenting you one of my fetish recipes for a traditional pizza-like treat that hails from beautiful Turkey.
"A quick poll of our friends revealed that most did indeed think of Turkish food as being limited to endless versions of oily braised eggplant, with a few sticky pastries and limp doner kebabs thrown in for good measure. Yet we had read plenty of books that described Turkish food as one of the greatest cuisines in the world, and numerous magazines and newspapers were busily printing stories about a revitalised Istanbul - the new 'cool' travel destination."
- Greg and Lucy Malouf
Apart from having amazing landscapes, photogenic sceneries and astonishing monuments, to die for eats, unique atmosphere and being romantically exotic, this incredible country placed at a crossroads between Europe and the Middle East is also the beholder of incredible culinary traditions that blow my mind away. With its Central and Far East Asian, Persian, Arabic, Balkanese and Mediterranean influences, the refined cuisine from "the land of the Turks" is so stunning and bewithchingly authentic that it is quite impossible not to fall under its irresistible charm.
Being a big fan of the gastronomy from this part of the world and a fervent admirer of the great Australian Lebanese-born chef Greg Malouf, I constantly crave the dishes that can be found in his three marvelously written as well as illustrated award-winning food and travel compendiums "Turquoise" (Turkey), "Saha" (Lebanon & Syria) and "Saraban" (Persia). They are a fantastic source of recipes and inspiration.
I have already tested a few of the specialities that this talented cook dispenses in his remarkable cookbooks. One in particular has been on the menu more than once and has never failed to sweep us off our feet. His succulent "Cheese, Suçuk And Olive Pide Pies" are terrific and so addictive.
Those scrumptious boat-shaped tarts known under the name of "Sucuklu Pide" are made with simple bread dough which is enriched with olive oil and garnished with halloumi, kasseri (or Mozarella if you can't find this Greek/Turkish stringy cheese), Kalamata olives, green bell pepper and a pungent sausage called suçuk. A wonderful delicacy that is lipsmackingly spicy, cheesy and bready. There sure is more to the Turkish cuisine than kebabs!
Submitted to Yeastspotting!
~ Cheese, Suçuk & Olive Pide Pies ~
Recipe adapted from Greg and Lucy Malouf's, "A Chef's Travels In Turkey: Turquoise".
Makes 3 medium (or 2 big) pide pies.
Ingredients For The "Pide":
1 x Pide dough (recipe follows)
250g Halloumi cheese, finely sliced (see remarks)
150g Mozarrella, finely sliced
12 Pitted Kalamata olives, cut in 4
1 Medium-sized green pepper, seeded and cubed
1 (240g) Suçuk sausage, sliced
Kirmizi biber (Turkish chilli powder, see remarks), to taste
Ground black pepper, to taste
1 Egg yolk
2 Tbs Milk
Ingredients For The "Pide Dough":
1/2 Tbs Dry yeast
A pinch castor sugar
190g/ml Warm water
250g Bread flour or all-purpose flour
3/4 Tsp Fine sea salt
2 Tbs Extra-virgin olive oil
Method For The "Pide Dough":
1. In the bowl of your mixer, dissolve the yeast in half the warm water and sprinkle with the sugar, set aside in warm place for 10 minutes or until frothy.
2. Incorporate enough flour to create a sloppy paste (similar in texture to pancake batter) and cover the bowl with a clean kitchen towel and let rest for 20 minutes in a warm place or until bubbly.
3. Add the remaining flour, the salt, water and the olive oil. Using the dough hook attachment, knead on low speed until the dough is smooth, springy and passes the window pane test, about for 10 minutes (add a little flour or water according to need - the dough should be slightly sticky, but not be tacky).
4. Transfer the dough to lightly oiled bowl, cover with plastic film, and let rest until doubled in size, about 1 1/2 hour.
5. Cut the dough into 3 equal portions and set aside.
Method For the "Pide":
6. Preheat the oven to 250° C (450° F).
7. Roll each piece of dough into a long 30 x 10cm (14 x 4 inches) rectangle.
8. Scatter 1/3 of the topping over the dough (start with the halloumi, then the mozarella, the olives, the pepper and the suçuk), leaving about a 2cm (1 inch) border around the edges.
9. Fold up the two long sides of the dough, bringing them up and over the topping, but without meeting in the middle, then squeeze the sides together at each end, twisting them together slightly to create a long "canoe/boat" shape. Sprinkle with the chilli powder and black pepper.
10. Repeat the operation with the rest of the dough.
11. To make the egg wash, mix together the yolk and the milk. Brush each pide with the egg wash.
12. Bake one Pide at a time for about 7 minutes, or until the bread is golden in color and the cheese has completely melted.
13. Serve hot.
If you don't have any halloumi, suçuk or kirmizi biber, you can replace them with quality Edamer cheese, Calabrese/dried or raw chorizo sausages and the chilli powder of your choice (fragrant and medium hot).
Serving Suggestions:
Serve with onion slices and a salad (tomato & cucumber or lettuce).
Sprinkle with additional olive oil and fine sea salt if you wish.
Recette adaptée du livre "A Chef's Travels In Turkey: Turquoise" par Greg and Lucy Malouf.
Pour 3 pide moyennes (ou deux grandes).
Ingrédients Pour La "Pizza Turque":
1 x Pâte à pain pour pide (la recette suit)
250g de Halloumi, tranché finement (voir remarques)
150g de Mozarrella, tranché finement
12 Olives kalamata, dénoyautées et coupées en lamelles
1 Poivron vert moyen, nettoyé et coupé en petits cubes
1 (240g) Saucisse suçuk sausage, coupée en rondelles
Kirmizi biber (poudre de piments turque, voir remarques), à volonté
Poivre noir, moulu, à volonté
1 Jaune d'oeuf
2 CS de lait
Ingrédients Pour La "Pâte A Pizza Turque":
1/2 CS de Levure sèche en poudre
190g/ml d'Eau tiède
Une pincée de sucre cristallisé
250g de Farine à pain ou farine blanche
3/4 CC de Sel de mer fin
2 Cs d'Huile d'olive extra vierge
Méthode Pour La "Pâte A Pizza Turque":
1. Dans le bol de votre robot, dissoudre la levure dans la moitié de l'eau, puis saupoudrer avec le sucre. Laisser reposer à température ambiante pendant 10 minutes, jusqu'à ce que le mélange soit mousseux.
2. Ajouter assez de farine afin de former une pâte visqueuse (telle une pâte à pancake). Recouvrir avec un linge de cuisine et laisser la "pâte" lever pendant 20 minutes à température ambiante.
3. Incorporer le reste de la farine et de l'eau, le sel et l'huile d'olive, puis pétrir dans votre robot (à l'aide du crochet) à basse vitesse pendant 10 minutes (ajouter de l'eau ou de la farine selon besoin - la pâte ne doit pas être collante) afin d'obtenir une pâte douce et élastique (elle doit passer le test du "vitrail").
4. Mettre la pâte dans un bol huilé, recouvrir avec du film plastique et laisser lever pendant 1 1/2 heures (la pâte doit avoir doublé de volume).
5. Couper la pâte en trois parts égales et mettre de côté (recouvrir avec un linge humide pour pas qu'elle sèche).
Méthode Pour La "Pizza Turque":
6. Préchauffer le four à 250° C.
7. Abaisser la pâte en un rectabgle de 30 x 10cm.
8. Recouvrir la pâte 1/3 de la avec la garniture (commencer avec le halloumi, puis continuer avec la mozarella, les olives, le poivron et la saucisse suçuk) tout en faisant attention de laisser un bord de 2cm de chaque côté.
9. Rabattre les deux bords de 30cm vers l'intérieur, sur la garniture, sans les faire se joindre (seulement les 2cm de pâte qui doivent être repliés), puis entortiller les bouts afin d'obtenir une forme de bâteau ("canoe"). Saupoudrer avec la poudre de piments et le poivre noir.
10. Répéter l'opération avec les deux autres parts de pâte.
11. Mélanger ensemble le lait et le jaune d'oeuf, et dorer les bords à l'aide d'un pinceau culinaire. 12. Cuire pendant environ 7 minutes, ou jusqu'à ce que la pâte soit cuite, dorée et que le fromage ait fondu.
13. Servir.
Si vous ne trouvez pas de halloumi, de suçuk ou de kirmizi biber, vous pouvez les remplacer par du Edamer de qualité, de la saucisse de Calabre/du chorizo cru ou séché de qualité et dela poudre de piments de votre choix (parfumé et pas trop épicée).
Idées de présentation:
Manger chaud et servir avec des oignons en rondelles et une salade (tomate et concombre ou laitue).
Si vous le désirez, vous pouver aussi ajouter un giclée d'huile d'olive et saupoudrer avec un peu de sel de mer fin.


text:
You are here
Award Data
The Award database is continually updated throughout the year. As a result, data for FY24 is not expected to be complete until March, 2025.
Download all SBIR.gov award data either with award abstracts (290MB)
or without award abstracts (65MB).
A data dictionary and additional information is located on the Data Resource Page. Files are refreshed monthly.
The SBIR.gov award data files now contain the required fields to calculate award timeliness for individual awards or for an agency or branch. Additional information on calculating award timeliness is available on the Data Resource Page.
Development of powder bed printing (3DP) for rapid and flexible fabrication of energetic material payloads and munitions
SBC: MAKEL ENGINEERING, INC. Topic: DTRA16A001This program will demonstrate how additive manufacturing technologies can be used with reactive and high energy materials to create rapid and flexible fabrication of payload and munitions. Our primary approach to this problem will be to use powder bed binder printing techniques to print reactive structures. The anticipated feedstock will consist of composite particles containing all reactant spe ...
STTR Phase I 2016 Department of DefenseDefense Threat Reduction Agency -
Portable and Automated Radiation Effects Test Structures for Advanced Technology Nodes
SBC: MICROELECTRONICS RESEARCH DEVELOPMENT CORPORATION Topic: DTRA16A003Micro-RDC will develop portable radiation effects test structures that scales to new process nodes. These structures will enable the investigation of the effects of radiation on the new technology from the material processing level as well as the circuit level. The production of the chosen structures and the development of software to extract the model parameters will form the framework. A suit ...
STTR Phase I 2016 Department of DefenseDefense Threat Reduction Agency -
Innovative Mitigation of Radiation Effects in Advanced Technology Nodes
SBC: RELIABLE MICROSYSTEMS LLC Topic: DTRA16A003Establish a radiation-aware analysis capability in a commercial EDA design flow that will enable first-pass success in radiation-hardened by design (RHBD) for DoD ASICs in much the same way that existing EDA design suites ensure first pass functionality and performance success of complex ASICs destined for commercial applications. Layout-aware, calibrated single-event radiation models that captur ...
STTR Phase I 2016 Department of DefenseDefense Threat Reduction Agency -
Modular Pulse Charger and Laser Triggering System for Large-Scale EMP and HPM Applications
SBC: SCIENTIFIC APPLICATIONS & RESEARCH ASSOCIATES, INC. Topic: DTRA16A004For effective protection against EMP and HPM threats, it is important to understand the physics of the threats, and also to quantify the effects they have on electrical systems. EMP and HPM vulnerability testing requires delivery of high peak power and electric fields to distant targets. The most practical solution to simulate such environments is to develop a modular, optically-isolated MV-antenn ...
STTR Phase I 2016 Department of DefenseDefense Threat Reduction Agency


text:
by Kevin Freking
WASHINGTON (AP) — The Obama administration's chief environmental watchdog, EPA Administrator Lisa Jackson, is stepping down after a nearly four-year tenure marked by high-profile brawls over global warming pollution, the Keystone XL oil pipeline, new controls on coal-fired plants and several other hot-button issues that affect the nation's economy and people's health.
Jackson, the agency's first Black administrator, constantly found herself caught between administration pledges to solve controversial environmental problems and steady resistance from Republicans and industrial groups who complained that the agency's rules destroyed jobs and made it harder for American companies to compete internationally.
The GOP chairman of the House Energy and Commerce Committee, Rep. Fred Upton, said last year that Jackson would need her own parking spot at the Capitol because he planned to bring her in so frequently for questioning. Republican presidential nominee Mitt Romney called for her firing, a stance that had little downside during the GOP primary.
Jackson, 50, a chemical engineer by training, did not point to any particular reason for her departure. Historically, Cabinet members looking to move on will leave at the beginning of a president's second term.
"I will leave the EPA confident the ship is sailing in the right direction, and ready in my own life for new challenges, time with my family and new opportunities to make a difference," she said in a statement. Jackson gave no exact date for her departure, but will leave after Obama's State of the Union address in late January.
In a separate statement, Obama said Jackson has been "an important part of my team." He thanked her for serving and praised her "unwavering commitment" to the public's health.
"Under her leadership, the EPA has taken sensible and important steps to protect the air we breathe and the water we drink, including implementing the first national standard for harmful mercury pollution, taking important action to combat climate change under the Clean Air Act and playing a key role in establishing historic fuel economy standards that will save the average American family thousands of dollars at the pump, while also slashing carbon pollution."
Environmental groups had high expectations for the Obama administration after eight years of President George W. Bush, a Texas oilman who rebuffed the agency's scientists and refused to take action on climate change. Jackson came into office promising a more active EPA.
But she soon learned that changes would not occur as quickly as she had hoped. Jackson watched as a Democratic-led effort to reduce global warming emissions passed the House in 2009 but was abandoned by the Senate as economic concerns became the priority. The concept behind the bill, referred to as cap-and-trade, would have set up a system in which power companies bought and sold pollution rights.
"That's a revolutionary message for our country," Jackson said at a Paris conference a few months after taking the job.
Jackson experienced another big setback last year when the administration scrubbed a clean-air regulation aimed at reducing health-threatening smog. Republican lawmakers had been hammering the president over the proposed rule, accusing his administration of making it harder for companies to create jobs.
She also vowed to better control toxic coal ash after a massive spill in Tennessee, but that regulation has yet to be finalized more than four years after the spill.
Jackson had some victories, too. During her tenure, the administration finalized a new rule doubling fuel efficiency standards for cars and light trucks. The requirements will be phased in over 13 years and eventually require all new vehicles to average 54.5 mpg, up from 28.6 mpg at the end of last year.
She shepherded another rule that forces power plants to control mercury and other toxic pollutants for the first time. Previously, the nation's coal- and oil-fired power plants had been allowed to run without addressing their full environmental and public health costs.
Jackson also helped persuade the administration to table the controversial Keystone XL pipeline, which would have brought carbon-heavy tar sands oil from Canada to refineries in Texas.
House Republicans dedicated much of their time this past election year trying to rein in the EPA. They passed a bill seeking to thwart regulation of the coal industry and quash the stricter fuel efficiency standards. In the end, though, the bill made no headway in the Senate. It served mostly as election-year fodder that appeared to have little impact on the presidential election.


text:
Get 10% off your first Library of America purchase.
Sign up for our monthly e-newsletter and receive a coupon for 10% off your first LOA purchase. Discount offer available for first-time customers only.
Phone orders: 1-800-964-5778 Request product #410432
ISBN: 978-1-59853-708-6 489 pages
LOA books are distributed worldwide by Penguin Random House


text: The image sharpen function (by Alex R. Austin) provided below seems to be very resource hungry and I couldn't make it work on two different servers - trying to sharpen a 413 x 413 image I ended up with "Fatal error: Allowed memory size of 8388608 bytes exhausted" or "Internal Server Error" or the script terminated without notice. Because I had no priviliges to change the default memory limit on these servers I started looking for other sharpen functions. I have come across a php Unsharp Mask function which works like a charm on both of the servers I dealt with. It can be found at http://vikjavev.no/hovudsida/umtestside.php.


text:
What should I Know Regarding Pregnancy, Nursing and Administering Antibiotic HC Solution to Children or the Elderly?
Sorry, we have no data available. Please contact your doctor or pharmacist.
Selected from data included with permission and copyrighted by First Databank, Inc. This copyrighted material has been downloaded from a licensed data provider and is not for distribution, except as may be authorized by the applicable terms of use.
CONDITIONS OF USE: The information in this database is intended to supplement, not substitute for, the expertise and judgment of healthcare professionals. The information is not intended to cover all possible uses, directions, precautions, drug interactions or adverse effects, nor should it be construed to indicate that use of a particular drug is safe, appropriate or effective for you or anyone else. A healthcare professional should be consulted before taking any drug, changing any diet or commencing or discontinuing any course of treatment.


text:
The federal government shutdown is in its 13th day, with little sign of a budget deal that could win the approval of both houses of Congress, as well as the White House. The debate now includes efforts to avoid a default if the government's debt limit isn't raised by Thursday.
Sunday afternoon, the White House reiterated its position after a phone call with House Minority Leader Nancy Pelosi, saying that she and President Obama agree on the need for "a clean [continuing resolution] and a one-year clean debt limit increase that would prevent a first-ever default of our nation's credit."
The reference to "clean" legislation stems from House Republicans' efforts to gut the Affordable Care Act, the health care system known as Obamacare.
But there were signs Sunday that while health care may have been the key issue in the House debate, in the Senate, which is now leading the discussion, a solution may hinge on the next round of sequestration cuts that take effect in January.
"[Senate Minority Leader Mitch] McConnell and Republicans want to continue current spending at $986.7 billion and leave untouched the new round of cuts in January, commonly known as sequester, that would reduce the amount to $967 billion," the AP reports. "Democrats want to figure out a way to undo the reductions, plus a long-term extension of the debt limit increase and a short-term spending bill to reopen the government."
Here's a roundup of what else people are saying about the state of affairs:
Sen. Chuck Schumer, D-N.Y., discussed undoing the sequester cuts — "one of the sticking points," he said — on CBS's Face the Nation:
"The dispute has been how to undo sequester. Republicans want to do it with entitlement cuts, in other words, take entitlement cuts and then put that money into undoing at least part of the sequester. Democrats want to do it with a mix of mandatory cuts, some entitlements, and revenues.
"And so how do you overcome that dilemma? We're not going to overcome it in the next day or two. But if we were to open up the government for a period of time that concluded before the sequester took place — which is Jan. 15 — we could have a whole bunch of discussions.
"And I am more optimistic than most we could come to an agreement. That was one place where the House Republicans and the president were not, you know, at total loggerheads."
On the same program, host Bob Schieffer asked Sen. John McCain, R-Ariz., how "a freshman senator, less than a year in office, Ted Cruz, was able to lead your party into what some in your party are calling a box canyon here? How did this happen?"
"There was already fertile ground because of those many members of the House who were elected in 2010 on the promise that they would repeal and replace Obamacare," McCain said said.
"And by the way, there were many of us who fought it back to 2009. We still want it changed. But to say that we were going to defund it just after the 2012 elections — every speech I gave all over the country were repeal and replace "Obamacare." Well, we lost. So we still can fight provisions of it. And the irony of all this is the rollout is a fiasco. That should be what's on the front page of newspapers across America."
McCain also criticized the president, saying that Obama hadn't been active enough in looking for solutions to get around the impasse.
"I hope the president will become engaged," McCain said. "Maybe we need to get — maybe we need to get Joe Biden out of the witness protection program," he said, referring to the vice president's ability to broker deals in Congress.
Sen. Amy Klobuchar, D-Minn., told host Candy Crowley on CNN's State of the Union: that she believes a deal will come before Thursday's deadline:
"I think you see the fact that Senator Reid, Senator McConnell are now talking and we've gotten to a stage where some of the demands that we've heard from House Republicans who put ideological things on the budget and shut the government down if they didn't defund Obamacare, if they didn't get something on on birth control, that's behind us now."
Later, she added,
"We have situations now where a plane manufacturer in Duluth, Minn., can't get their inventory out of a warehouse to be able to try to sell it overseas, where they do exports all the time, because the Transportation Department shut down and they can't get approvals. We have fishermen off Alaska that are going to lose their market on crab to Russia. It's an unbelievable thing. We have to get this government open again."
Sen. Lindsey Graham, R-S.C., tells George Stephanopoulos on ABC's This Week that any deal should start in the House.
"Here's what I'm worried about: a deal coming out of the Senate that a majority of Republicans can't vote for in the House. That really does compromise Speaker Boehner's leadership. And after all this mess is over, do we really want to compromise John Boehner as leader of the House? I don't think so.
"So I'm not going to vote for any plan that I don't think can get a majority of Republicans in the House — understanding that defunding Obamacare and delaying it for a year is not a realistic possibility now."
Later, Graham said:
"We're in a free-fall as Republicans, but Democrats are not far behind. And after listening to all of us talk now, I probably understand why 60 percent of Americans want to vote all incumbents out.
"To my colleagues in the House on both sides, and to my friends in the Senate: we are ruining both institutions."
How federal judges view the shutdown — particularly after a sequester that took a toll on the judiciary — is the topic of a Politico report today.
Senior U.S. District Judge Richard Kopf, who writes a blog (called Hercules and the Umpire) apart from his bench duties in Nebraska, wrote last week that "It is time to tell Congress to go to hell. It's the right thing to do."
"Court budgets have essentially been slashed to the bone, with us losing nationwide thousands of judicial employees performing very important tasks...We're being told to furlough where we're already cut to the bone," Judge Richard Roberts, whose district court is near the Capitol, tells Politico.
The website also notes that Judge Amy Berman Jackson rebuffed an attempt to keep a House-related court case moving, despite the shutdown. Here's how she responded to House lawyers who sought to keep their inquiry into Operation Fast and Furious moving along:
"While the vast majority of litigants who now must endure a delay in the progress of their matters do so due to circumstances beyond their control, that cannot be said of the House of Representatives, which has played a role in the shutdown that prompted the stay motion," Jackson wrote.
And earlier today on NPR's Weekend Edition, you could hear a report on Senate Chaplain Barry C. Black, who hasn't spared the chamber from a bit of scolding during the shutdown.
Copyright 2021 NPR. To see more, visit https://www.npr.org.