Gurjeet Singh writes:
Thus, writing a pattern that actually matches a literal backslash means
writing four backslashes in the statement.
Thanks.
select * from mytable where f1 like '%%';
Worked.
For the archives..
After reading section 4.1.2.2
Also found that these other one also wor
On Mon, May 19, 2008 at 7:56 AM, Francisco Reyes <[EMAIL PROTECTED]>
wrote:
> Is there a way to search for rows with the character \?
>
> I tried variants of like and ~.
>
> create table mytable (f1 text);
> insert into mytable values ('Test row 1');
> insert into mytable values (E'Test row 2 \\'
Is there a way to search for rows with the character \?
I tried variants of like and ~.
create table mytable (f1 text);
insert into mytable values ('Test row 1');
insert into mytable values (E'Test row 2 \\');
select * from mytable where f1 like E'%\\%'; <-- returned nothing
select * from myta
[see below]
Kerri Reno wrote:
Vance,
I missed your earlier post, so I may be misunderstanding the
situation, but I think you could do this more easily in plpython,
because TD['new'] and TD['old'] are dictionaries, and you can traverse
the dictionaries like this:
for k, v in TD['new'].items
> I want it so that every operation on db1.table1 (ie. INSERT, UPDATE, DELETE)
> also happens to db2.table2, but similarly I want it that application can do
> those operations on db2.table2 but actually it does it on db1.table1 behind
> the scene.
If the tables could be in the same database but
Tom Lane wrote:
What I think *is* worth doing is spending some time on making dictionary
loading go faster.
This is probably a stupid question, but: with PostgreSQL's use of shared
memory, is it possible to load dictionaries into a small reserved shm
area when the first backend starts, then
On Sun, May 18, 2008 at 8:04 AM, Ivan Sergio Borgonovo
<[EMAIL PROTECTED]> wrote:
> What is the effect of having nested functions all declared
> SERIALIZABLE?
>
> What if just the outermost is declared SERIALIZABLE?
SERIALIZABLE applies to the entire transaction, not to individual
function calls.
Teodor Sigaev <[EMAIL PROTECTED]> writes:
>> Hmm, good point; I presume "accept the fact that settings change won't
>> propagate to other backends until reconnect" would not be acceptable
>> behavior, even if documented along with the relevant configuration option?
> I suppose so. That was one o
alisazegar <[EMAIL PROTECTED]> writes:
> I'm having difficulties with Postgres lately. Postgres service for (pgsql
> 8.2 )kept stopping every few minutes.
> Then I read a note somewhere saying that there is a bug in 8.2 which causing
> the problem.
> I switched to 8.3 and have the same problem.
>
Teodor Sigaev wrote:
As for downsides, I only really see two:
* Tracking updates of dictionaries - but it's reasonable to believe
that new connections get open more often than the dictionary gets
updated. Also, this might be easily solved by stat()-ing the
dictionary file before starting up s
Reuben D. Budiardja wrote:
Hello,
Suppose I have two tables db1.table1 and db2.table2. Is there anyway I can
actually have db2.table2 a link to db1.table1 ? What I meant is similar to a
symlink in Unix filesystem (db2.table2 is a symlink to db1.table1).
I want it so that every operation on db
Hmm, good point; I presume "accept the fact that settings change won't
propagate to other backends until reconnect" would not be acceptable
behavior, even if documented along with the relevant configuration option?
I suppose so. That was one of the reasons to move tsearch into core and it wi
Michael P. Soulier wrote:
Is there a simple way to update the row, and cascade the change to any
and all rows referencing this row as a foreign key? I searched on
cascade in the postgres docs and while I found references to deletion, I
didn't find one for updates.
http://www.postgresql.org/d
Hi,
I have to update a row of data that is referenced via a foreign key
constraint from another table.
I cannot change the id of the referenced record because it is referenced
as a foreign key from another table.
Is there a simple way to update the row, and cascade the change to any
and al
alisazegar wrote:
Hi All,
I'm having difficulties with Postgres lately. Postgres service for (pgsql
8.2 )kept stopping every few minutes.
Then I read a note somewhere saying that there is a bug in 8.2 which causing
the problem.
I switched to 8.3 and have the same problem.
It's running happily
Hi All,
I'm having difficulties with Postgres lately. Postgres service for (pgsql
8.2 )kept stopping every few minutes.
Then I read a note somewhere saying that there is a bug in 8.2 which causing
the problem.
I switched to 8.3 and have the same problem.
What I found so far is that the last eve
On Fri, 16 May 2008 09:55:56 -0400
Andrew Sullivan <[EMAIL PROTECTED]> wrote:
> On Fri, May 16, 2008 at 09:06:11AM +0200, Ivan Sergio Borgonovo
> wrote:
> > Is
> > BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE
> > what I'm looking for?
> Yes.
Perfect, thanks.
What is the effect of having neste
* Considering the database is loaded separately for each session, does
this also imply that each running backend has a separate dictionary
stored in memory?
Yes.
As for downsides, I only really see two:
* Tracking updates of dictionaries - but it's reasonable to believe
that new connection
I've been having problem with pgsql-8.2.5 master/slave warm standby
replication setup where occasionally master node generates a wal file
smaller then expected 16MB. pg_standby on slave gets stuck on such short
files, and replication halts from that moment on. we have to do
pg_start_backup/ rsy
postgres 2.5 ??? wow ... that's an old version... Consider an upgrade...
>From what i know, it shouldn't be a problem, because it's primarily the same
sub-version... It would be another story if it was from 2.5 to 2.6 (in that
case, you should use pg_dump_all) ... But i really don't know if with a
20 matches
Mail list logo
