On Sun, Dec 16, 2012 at 06:30:24PM -0500, Steve Clark wrote:
> why not use the squeeze option of tr.
>
> tr -s " "
I wasn't aware of that one, it's even simpler and more elegant.
Thanks!
For this particular case, tr(1) won't do for the same reason
the simple sed(1) expression I gave won't do: it
On Sun, Dec 16, 2012 at 11:17:25AM -0800, Adrian Klaver wrote:
> On 12/16/2012 11:07 AM, Peter Bex wrote:
> > I don't know how Postgres stores its passwords internally or how
> > its authentication works exactly. Maybe one of the developers
> > can shine
On Sun, Dec 16, 2012 at 07:42:40PM +0100, Murray Cumming wrote:
> On Sun, 2012-12-16 at 17:51 +0100, Peter Bex wrote:
> > Hashes (if properly salted and
> > stretched) are only useful if they are only ever checked against the
> > password itself. Storing a hash of any ki
On Sun, Dec 16, 2012 at 01:30:29PM -0500, Tom Lane wrote:
> Peter Bex writes:
> > On Sun, Dec 16, 2012 at 12:51:08PM -0500, Tom Lane wrote:
> >> Right, they can break into *this account*.
>
> > Not *just* this one, but any account on any service that uses this
>
On Sun, Dec 16, 2012 at 06:48:35PM +0100, Andreas wrote:
> With sed as startingpoint I figured it out.
> Those 3 steps make the input files consumable for COPY
>
> 1. dos2unix
> 2. sed -i 's/[ \t]*$//'
> 3. sed -i 's/ / /g'
You can reduce this to one invocation by separating the commands
by a se
On Sun, Dec 16, 2012 at 12:51:08PM -0500, Tom Lane wrote:
> Peter Bex writes:
> > If they do break in and are able to retrieve the password hash, they
> > can still break in with that hash.
>
> Right, they can break into *this account*.
Not *just* this one, but any accoun
On Sun, Dec 16, 2012 at 05:51:23PM +0100, Peter Bex wrote:
> The best solution I can come up with is not provide a web UI at all
> but let the user connect directly to the database using a secure
> method (e.g. SSL client certs, GSSAPI etc).
Speaking of which, a custom implementati
On Sun, Dec 16, 2012 at 05:38:37PM +0100, Murray Cumming wrote:
> On Sun, 2012-12-16 at 17:24 +0100, Peter Bex wrote:
> > What's the use of that?
> [snip]
>
> I would not be storing the plaintext password anywhere. That makes it
> harder for someone get the plaintext p
On Sun, Dec 16, 2012 at 04:54:30PM +0100, Murray Cumming wrote:
> libpq lets me open a connection by specifying a password:
> http://www.postgresql.org/docs/9.2/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS
>
> Is there any way to specify a hash of the password when connecting, instead
> of
> pr
On Sat, Dec 15, 2012 at 10:16:55PM +0100, Peter Bex wrote:
> A simple sed(1) expression should do the trick:
>
> sed -E 's/ +/ /g' old-file > new-file
I just remembered where I could check, and the GNU sed equivalent is:
sed -r 's/ +/ /g' old-file > new-fil
On Sat, Dec 15, 2012 at 08:06:44PM +0100, Andreas wrote:
> Hi,
>
> Problem here is in the morning the first digit of the hour is shown as a
> blank so there are 2 blanks before the time so COPY misstakes this as an
> empty column and gets confused.
>
> Can someone point me in the direction of a
On Sat, Sep 01, 2012 at 12:43:15AM +0200, Geert Mak wrote:
> There is this case studies section as well -
>
> http://www.postgresql.org/about/casestudies/
>
> Which appear to me a little old and a little too little, one could try to add
> more, perhaps.
I noticed that the "Share Your Story" lin
On Thu, Jul 26, 2012 at 08:17:19AM -0400, Chris Curvey wrote:
> 1) a tool for power users to be able to get their own data. There are
> a few folks here who are smart enough to be trusted with direct access
> to the database, but I don't want to ask them to learn SQL. Something
> like an open sou
On Tue, Jun 19, 2012 at 02:20:57AM -0400, Tom Lane wrote:
> Craig Ringer writes:
> > I've been working in psql a lot recently, and have started to wonder why
> > statements with syntax errors or other problems that render them
> > unexecutable terminate the transaction.
>
> Well, the obvious re
On Thu, May 03, 2012 at 09:39:29AM +0200, Alexander Reichstadt wrote:
> Thanks, that's answering my question. In Objective-C as well as many other
> languages there is the feature to turn on Garbage Collection. It's a separate
> thread that scans memory for strong pointers, their source and origi
On Thu, May 03, 2012 at 09:08:53AM +0200, Alexander Reichstadt wrote:
>
> Hi,
>
> since I got no answer so far I searched through the docu again. I searched
> for GC as well as Garbage, and all garbage refers to is with regard to
> vacuuming a database. But my question refers to wether or not m
On Thu, Mar 15, 2012 at 05:09:32PM -0600, Doug Gorley wrote:
> G'day,
>
> "select * from tdt_unsent where str_name_l = 'SMITH'" returns 0 rows.
> "select * from tdt_unsent where str_name_l ~ '^SMITH'" returns 3 rows.
> "select * from tdt_unsent where str_name_l ~ '^SMITH$'" returns 0 rows.
> "sele
On Sun, Aug 14, 2011 at 10:39:48AM -0400, W. Matthew Wilson wrote:
> I'm sure I'm not the first person to end up with a gigantic query that
> does lots of left joins and subselects.
>
> It seems to work, but I would love to break it up into smaller chunks.
>
> I'm thinking about rewriting the que
On Wed, Jul 27, 2011 at 04:35:45PM +0200, Karsten Hilbert wrote:
> > I wonder which other languages have first class support for these areas of
> > Pg?
>
> While already supporting most if not all standard PG datatypes the
> psycopg2 interface lets you write in/out wrappers of arbitray
> complexit
On Sun, Jun 26, 2011 at 11:23:30PM +0200, Dave Coventry wrote:
[snip]
> 2011-06-26 17:13:24 EDT DETAIL: Failed system call was
> shmget(key=5432001, size=29278208, 03600).
> 2011-06-26 17:13:24 EDT HINT: This error usually means that
> PostgreSQL's request for a shared memory segment exceeded ava
On Sun, Jun 26, 2011 at 09:36:59PM +0200, Dave Coventry wrote:
> I'm having huge problems with a Drupal install using Postgres 8.4.8.
>
> I'm getting the following error:
Do you get the error in the logs or do you see it while going to the
site manually and does it show this instead of rendering
On Thu, Jun 16, 2011 at 05:19:41PM -0400, Tom Lane wrote:
> Peter Bex writes:
> > But when I try to do the same but pas the 2 as a parameter,
> > (I do "EXECUTE bar($1)" with $1 bound to "2"), I get an error:
>
> Why would you do that, rather than executi
Hi all,
I'm seeing a bit strange (some might say inconsistent) behaviour,
possibly a bug.
First, I prepare a statement by running the query:
"PREPARE bar (int) AS (SELECT 1, $1, 3)"
Then I try to use the generic libpq query function PQsendQueryParams
with a query of "EXECUTE bar(2)" and I ge
On Wed, Nov 24, 2010 at 09:37:02AM +, Grzegorz Jaśkiewicz wrote:
> just never use SELECT *, but always call columns by names. You'll
> avoid having to depend on the order of columns, which is never
> guaranteed, even if the table on disk is one order, the return columns
> could be in some other
Hello all,
I'm not sure if this would be considered off topic, but I'd like to
point out this week's issue of the Chicken Gazette in which I describe
integration of array and "ROW" composite type handling with the
PostgreSQL library for the Chicken Scheme compiler:
http://gazette.call-cc.org/issue
On Fri, Nov 12, 2010 at 10:18:31AM +0100, Thomas Kellerer wrote:
> The hstore module would also be a viable alternative - and it's indexable
> as well.
That's what the post I replied to mentioned :)
Also, when I looked at hstore, it had a limitation on its length which
made it a little dangerous
On Fri, Nov 12, 2010 at 10:43:14AM +0300, Dmitriy Igrishin wrote:
> Hey Peter,
>
> Unfortunately, there is no indexes on arrays (only on expressions).
> With hstore we can easily create GiST index for effective access.
True. In my project I only ever needed to search on a particular key,
and I ma
On Fri, Nov 12, 2010 at 10:17:50AM +0300, Dmitriy Igrishin wrote:
> Hey Mark,
>
> Yeah, I can't imagine an entity in a real project even with more than 100
> columns. Its rare case.
> But if you entities (rows/tuples) of some class (table) can contains
> variable
> set of columns (properties) you
On Fri, Oct 22, 2010 at 08:20:11PM +0400, Dmitriy Igrishin wrote:
> Hey Peter,
Hello Dmitriy,
> > As far as I can see, this would imply either creating views on the
> > for every user (or company?), or manually crafting queries
> > to do the same. The latter is of course what most webapps do, an
On Fri, Oct 22, 2010 at 12:21:17AM +0400, Dmitriy Igrishin wrote:
> Hey Tony,
>
> 2010/10/21 Tony Cebzanov
>
> > I have a web application with a Postgres backend. In my initial
> > prototype, I decided not to have a Postgres database user created for
> > each application user, opting instead to
On Wed, Sep 29, 2010 at 07:33:53PM +0100, Thom Brown wrote:
> Okay, I understand what's happening. But does the planner need to
> understand the type of literals in the select list if it's not used
> anywhere else?
Fields sent back to the client also carry their type with them.
There's no "unknow
On Wed, Sep 29, 2010 at 07:08:22PM +0100, Thom Brown wrote:
> Could someone explain why the following doesn't work?
>
> test=# PREPARE meow(unknown) AS
> test-# SELECT $1 as meow;
> ERROR: could not determine data type of parameter $1
>
> The problem is that using PDO in PHP, prepared statements
On Fri, Aug 06, 2010 at 02:25:27PM -0600, Scott Marlowe wrote:
> For an extra added bonus, show a click-path from the front page
> mysql.com to the documentation. I gave up and just entered
> mysql.com/documentation which kicked off the search engine and let me
> click somewhere into the 5.1 docs.
On Fri, Aug 06, 2010 at 02:09:43PM -0600, Scott Marlowe wrote:
> I'm all in favor of a nice tutorial section in the docs. But I
> certainly don't want pgsql docs to mimick the mysql docs method of
> using a tutorial method for most of the beginner information. It's so
> dang hard to find anything
On Wed, Jul 28, 2010 at 02:05:47PM -0500, P Kishor wrote:
> each row is half a dozen single byte values, so, it is actually 6
> bytes per row (six columns). Even if I combine them somehow, still the
> per row overhead (which, I believe, is about 23 bytes) is more than
> the data. But, that is not t
On Fri, Apr 16, 2010 at 11:28:36AM -0400, Merlin Moncure wrote:
> If you are storing big data and want to keep the overhead low, the
> first thing you need to examine is organizing your data into arrays.
> This involves tradeoffs of course and may not work but it's worth a
> shot!
That does sound
On Fri, Apr 16, 2010 at 12:40:21PM +0200, Szymon Guz wrote:
> I thought that the default fillfactor was much smaller (and haven't checked
> that now)... sorry for messing that up.
> But let's think of it from the other side: what do you want to do with that
> data? Maybe PostgreSQL with it's MVCC'
On Fri, Apr 16, 2010 at 11:59:38AM +0200, Szymon Guz wrote:
> File pages are not fully filled from the start as that could result in bad
> performance of queries later.
The manual page you linked to says something else:
"The fillfactor for a table is a percentage between 10 and 100.
100 (complete
Hi all,
I have a table with three columns: one integer and two doubles.
There are two indexes defined (one on the integer and one on one
of the doubles). This table stores 70 records, which take up
30 Mb according to pg_relation_size(), and the total relation size
is 66 Mb.
I expected the di
On Thu, Apr 01, 2010 at 04:37:23PM -0400, Tom Lane wrote:
> There is not, but you could always look at the source for array_out and
> array_in if you want definitive answers ;-). Personally what I'd do is
> always double-quote each non-null array element; then the rules reduce
> to "backslash any
Hello all,
I am currently adding array value handling to the PostgreSQL interface
for the Chicken Scheme compiler[*] and I was wondering if there's a more
detailed documentation for the exact syntax of arrays than the short
natural language explanation in the manual.
There doesn't appear to be a
41 matches
Mail list logo
