On Thu, Oct 10, 2013 at 3:44 AM, Torsten Förtsch
wrote:
> Hi,
>
> assuming a constraint is added to a table as NOT VALID. Now I know it IS
> valid. Can I simply declare it as valid by
>
> update pg_constraint
>set convalidated='t'
> where conrelid=(select c.oid
>from pg_cl
On Sat, Oct 12, 2013 at 12:56 AM, akp geek wrote:
> We have been running 4 of our applications on 9.0.4, which we are planning
> to update the database 9.2.2 by the year end. we have the streaming
> replication also running
9.2.4 has fixed a severe security problem. If you do not want to
expose yo
Hello
Why? There are no multilevels structures in pg. Variables should be joined
with schemas or extensions. Other levels are messy.
-
"M Better"
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/postgres-9-0-4-configuration-and-performance-issue-tp5774309p577436
> My interpretation of "Forms these days are written in HTML" means
> most interfaces are web front ends to the cloud. Not a GUI framework.
"Cloud", "web apps", yet more fashionable trendslang buzzwords.
I am talking about worktools that actually help productive "information
workers" to get usefu
> >> Forms these days are written in HTML.
> >
> > Only by clueless/careless morons.
> >
> > HTML has never been, is not and will never be a usable GUI
> > framework.
> >
> > And "web apps" are unusable garbage.
>
> Look -- I appreciate people with strong unorthodox beliefs but your
> statement ab
Hi,
What does it mean if the Error: 'argument exceeds the maximum length of 1024 bytes' is raising using psql.
How can I increase this limit?
Janek Sendrowski
On 10/12/2013 06:39 AM, Wolfgang Keller wrote:
Certainly not. Not to mention the issue of end-user productivity. Not
to mention the deployment mess, both server- *and* client-side, with
"web apps". Etc. and so on...
Five years ago I would have agreed with you totally. Web applications
where
On sob, paź 12, 2013 at 06:30:51 +0200, jane...@web.de wrote:
>What does it mean if the Error: 'argument exceeds the maximum length of
> 1024 bytes' is raising using psql.
>How can I increase this limit?
How did you achieve it? Can you show screenshot of what you did, and how
the error wa
I would say it's just a query with to many rows or something like that.
My query was: SELECT jaro('word', col) FROM table.
The tables has ca. 75000 rows. If I'm gonna use the WHERE condition and only
select the first 1 rows, it's working.
So it could be something with the memory, but 1024 byte
what is in function jaro?
Dne 12. 10. 2013 19:22 "Janek Sendrowski" napsal(a):
> I would say it's just a query with to many rows or something like that.
> My query was: SELECT jaro('word', col) FROM table.
> The tables has ca. 75000 rows. If I'm gonna use the WHERE condition and
> only select the
Hello
I looked to source code and this error message is only in fuzzystrmatch
extension. Please, next time, specify a PostgreSQL version number, and used
extensions.
I looked to source code, and these limits are defined in
/contrib/fuzzystrmatch/ levenshtein.c or fuzzystrmatch.c - you can find
t
PG 9.3, consider a table test like:
tz timestamp not null,
cola varchar not null,
colb varchar not null
2 compound indexes:
tz_cola on (tz, cola)
tz_colb on (tz, colb varchar_pattern_ops)
now a query, for some start & end timestamps:
select * from test where tz >= start and tz < end and colb l
Le samedi 12 octobre 2013 à 15:39 +0200, Wolfgang Keller a écrit :
> "Web mailers" are a particularly illustrative example why "web apps" are
> ridiculous garbage. Just like "web forums" or "Google Apps".
>
> If I had to use those, I would cease to use computers at all.
>
Sure, they suck, but I
Browsers are fine for displaying informaiton that is already in a
database. They are the ultimate crap for entering data that has to be
typed into a "form" and processed for persistence. It will be a long time
before I ask my users to enter data into a browser.
Just for an example: If you have
On 10/12/2013 12:19 PM, Chuck Davis wrote:
Browsers are fine for displaying informaiton that is already in a
database. They are the ultimate crap for entering data that has to be
typed into a "form" and processed for persistence. It will be a long
time before I ask my users to enter data into a
Le samedi 12 octobre 2013 à 12:19 -0700, Chuck Davis a écrit :
> Just for an example: If you have 500 clients placing one order a
> browser is an "ok" tool -- probably the tool of choice. If you have
> one accounts payable clerk entering 500 orders a browser is a very
> mean thing to do the your
On 10/12/2013 01:14 PM, Vincent Veyron wrote:
Le samedi 12 octobre 2013 à 12:19 -0700, Chuck Davis a écrit :
Just for an example: If you have 500 clients placing one order a
browser is an "ok" tool -- probably the tool of choice. If you have
one accounts payable clerk entering 500 orders a br
On 12/10/13 20:08, Scott Ribe wrote:
> select * from test where tz >= start and tz < end and colb like '%foobar%'
I think you can use an index only for wildcard expressions that are
anchored at the beginning. So,
select * from test where tz >= start and tz < end
and colb like 'foobar%'
ca
Adrian Klaver-3 wrote
> pv150el90 = PVC 1.5" ell 90 degree
> abs150el90 = ABS 1.5" ell 90 degree
You can code an interactive command line processor in pretty much any
language - html+javascript included. The issue is likely one generalized to
GUI in particular since now that people are used to ha
On Sat, Oct 12, 2013 at 11:08 AM, Scott Ribe
wrote:
[skipped]
> select * from test where tz >= start and tz < end and colb like '%foobar%'
>
> Assume that the tz restriction is somewhat selective, say 1% of the table,
> and the colb restriction is extremely selective, say less than 0.1%.
[s
On 10/12/2013 02:40 PM, David Johnston wrote:
Adrian Klaver-3 wrote
pv150el90 = PVC 1.5" ell 90 degree
abs150el90 = ABS 1.5" ell 90 degree
You can code an interactive command line processor in pretty much any
language - html+javascript included. The issue is likely one generalized to
GUI in p
Hi Chuck,
>
> Could you explain the acronym AP?
>
> I understand that there are lots of situations I have not met yet, so
> this might explain my ignorance, but I don't see what you get from using
> a client-side app over a browser for most databases uses; after all,
> from the user's point of vie
Scott Ribe writes:
> PG 9.3, consider a table test like:
> tz timestamp not null,
> cola varchar not null,
> colb varchar not null
> 2 compound indexes:
> tz_cola on (tz, cola)
> tz_colb on (tz, colb varchar_pattern_ops)
> now a query, for some start & end timestamps:
> select * from test wher
On Oct 12, 2013, at 4:21 PM, Tom Lane wrote:
> The reason you're losing on this is that the "select *" command eliminates
> the possibility of an index-only scan (I'm assuming that that selects some
> columns that aren't in the index). Given that a plain indexscan will
> always involve fetching
On 12/10/2013 23:15, Chuck Davis wrote:
For those of us who grew up on real computers the only appropriate way
to get from one input field to the next is hitting the enter key. You
know what that does in a browser...makes efficient data input
impossible. NOBODY should have to hit the tab key
On 13/10/2013, at 9:15 AM, Chuck Davis wrote:
> the only appropriate way to get from one input field to the next is hitting
> the enter key.
Ha, I remember how blazing fast entry could be on old terminals with a field
exit key on the numeric keypad - particularly when standardised on 4-6 dig
On 10/12/2013 6:15 PM, Chuck Davis wrote:
For those of us who grew up on real computers the only appropriate way
to get from one input field to the next is hitting the enter key. You
Well, I grew up with a real computer. There was no enter key on the 029
key punch; that only came along later
27 matches
Mail list logo
