En un mensaje anterior, Greg Smith escribió:
> >So, any way of instructing PG (8.1 if that matters) to place those
> >files elsewhere without an initdb?
> >
>
> You can create another table just like the original on a tablespace
> using the new storage, drop the original, and then rename the n
Hi,
I have a big database on FS1, now almost full. Have space on FS2,
where I created a tablespace and moved every table and index to it.
Still, lots of space used on FS1. The problem is not pg_xlog, but
base:
# du -hs base/105658651/* | fgrep G
1,0Gbase/105658651/106377323
1,0Gbase/10
En un mensaje anterior, Merlin Moncure escribió:
> On Tue, May 13, 2008 at 8:50 AM, Fernando Schapachnik
> <[EMAIL PROTECTED]> wrote:
> > > > ALTER SEQUENCE name [ INCREMENT [ BY ] increment ]
> > > >[ MINVALUE minvalue | NO MINVALUE ] [ MAXV
En un mensaje anterior, Merlin Moncure escribió:
[...]
> >> > Am I doing something wrong?
> >>
> >> yes and no when you created the table initially you probably made it
> >> a 'serial' column which set up the ownership that prevents the drop
> >> operation. that ownership did not go away when you
En un mensaje anterior, Merlin Moncure escribió:
> On Thu, May 8, 2008 at 7:52 AM, Fernando Schapachnik
> <[EMAIL PROTECTED]> wrote:
> > Pg 8.1.11, I try to change sequences as default value of a table, then
> > remove old sequence:
> >
> > # \d table1
>
Pg 8.1.11, I try to change sequences as default value of a table, then
remove old sequence:
# \d table1
Table "table1"
Column | Type | Modifiers
+-+---
id
En un mensaje anterior, Michael Glaesemann escribió:
>
> On Jun 22, 2007, at 10:16 , Fernando Schapachnik wrote:
>
> >EXPLAIN SELECT DISTINCT p.id
>
> Can you provide EXPLAIN ANALYZE? I suspect that when you rewrote the
> query it changed how the planner took into ac
En un mensaje anterior, Tom Lane escribió:
> Fernando Schapachnik <[EMAIL PROTECTED]> writes:
> > Now, combined (sorry for the convoluted query, it is build
> > automatically by an app).
>
> > EXPLAIN SELECT DISTINCT p.id
> > FROM partes_tecnicos p
En un mensaje anterior, Tom Lane escribió:
> Fernando Schapachnik <[EMAIL PROTECTED]> writes:
> > Now, combined (sorry for the convoluted query, it is build
> > automatically by an app).
>
> > EXPLAIN SELECT DISTINCT p.id
> > FROM partes_tecnicos p
Maybe this is already solved in more advanced releases, but just in
case.
VIEW active_users:
SELECT * FROM users WHERE active AND ((field IS NULL) OR (NOT field));
Table users has index on text field login.
EXPLAIN SELECT * from active_users where login='xxx';
En un mensaje anterior, Tom Lane escribió:
> PG versions before 8.2 don't handle very long IN lists particularly
> well. This query will take a fair amount of stack space to parse, not
> to mention an unreasonably long time to plan. (You should consider
> putting the 16000 values in a temp table
En un mensaje anterior, Tom Lane escribió:
> Fernando Schapachnik <[EMAIL PROTECTED]> writes:
> > I've stumbled upon what seems to be a core-dumping infinite recursion
> > in transformExpr(), on 8.1.6.
>
> A test case would help.
The culprit query looks like:
I've stumbled upon what seems to be a core-dumping infinite recursion
in transformExpr(), on 8.1.6.
Backtrace:
Core was generated by `postgres'.
Program terminated with signal 10, Bus error.
Reading symbols from /usr/lib/libssl.so.3...(no debugging symbols
found)...done.
Loaded symbols for /usr
En un mensaje anterior, Matt Van Mater escribió:
> I there a way to specify that I want the contribs directory (and its
> children) compiled and installed during the build process in the
> various BSD ports systems? Of course I understand that what works on
> one BSD may not work on the others, bu
I'm trying to figure out why Samba is failing at high loads if using Postgres as
a backend (7.3.9 in my setup). On startup in makes one connection only against
the database which is shared among all the Samba processes. In turn, each issue
a PQexec() over the same connection (a SELECT, actually). I
Hi,
I'm trying to use an SSL-enabled (OpenSSL 0.9.7d) Postgres 7.3.9 as database
backend to Samba 3.0.11. On startup Samba opens a connection, and passes it to
every fork()ed process. On some scenarios (consistenly, when somebody tries to
log into a workstation after reboot), Samba spits:
SELE
Just kill the processes. You can grep for postgres AND idle. It doesn't prevent
new connections, but doesn't look like an issue in your scenario. If you need
that, you can restart with a copy of pg_hba.conf that only allows localhost, do
your drop & recreate, and then restart again.
Regards.
sleect function(ssd_a) from ...
where function is one of the built-in text function or one of your own written
in some of the supported (by your version) procedure languages.
Regards.
En un mensaje anterior, srini vasan escribió:
> --- srini vasan <[EMAIL PROTECTED]> wrote:
>
> > Hi
> >I a
Try gmake.
Regards.
En un mensaje anterior, David Wheeler escribió:
> 4.8-STABLE FreeBSD 4.8-STABLE i386
>
> sahlins# cd postgresql-7.4.2/contrib/pg_autovacuum
> sahlins# make
> "../../src/Makefile.global", line 38: Missing dependency operator
---(end of broadcast)-
En un mensaje anterior, scott.marlowe escribió:
> On Sat, 17 Jan 2004, Joshua D. Drake wrote:
>
> > Hello,
> >
> > Well... 7.4 to 7.4.1 is a direct upgrade. You do not have to do a
> > reinitdb which means you do
>
> You may have missed where bill said he wanted to change a default limit
> f
En un mensaje anterior, scott.marlowe escribió:
> > 2) I would like to upgrade to 7.4.1 without having to re-edit any config
> > files or change any paths.
>
> Just backup the config files in $PGDATA to another directory, and toss
> them back into $PGDATA after the initdb
>
> > 3) I would like t
Take a look at datasize: your processes are allowed a maximum of 512 Mb RAM.
Read the handbook to find out how to reconfigure your kernel and the limits
(and/or ulimit) man page to tweak the values for individual processes.
Good luck!
Fernando.
En un mensaje anterior, Sean Shanny escribió:
> lim
Is your system using full RAM? Ie, what does limits -a show?
Regards.
Fernando.
En un mensaje anterior, Sean Shanny escribió:
> To all,
>
> The facts:
>
> PostgreSQL 7.4.0 running on BSD 5.1 on Dell 2650 with 4GB RAM, 5 SCSI
> drives in hardware RAID 0 configuration. Database size with inde
Looks like the new DB might have been initialized with a different locale. Read
about locales and initdb in the docs.
Good luck.
Fernando.
En un mensaje anterior, Pedro Miguel Guedes escribió:
[...]
>
> The problem seems to be on accent on letters. So I thought maybe some stuff
> on charsets/en
> <[EMAIL PROTECTED]> writes:
> > I HAVE used pg_dumpall -g to make a backup of of users and groups, but
> > this output does not include the ALTER DATABASE commands.
Another related problem. pg_dump/pg_restore doesn't properly restore GRANT
CREATE ON DATABASE
pg_restore --create db.dump:
--Samp
En un mensaje anterior, Giorgio Volpe escribió:
> May be it's my ignorance about sql ...
> but why cannot i use alias name of a column in a where clause?
>
>
> # select key as cc from mytable where cc > 0;
> ERROR: Attribute 'cc' not found
AFAIK you can't use alias in ther where part.
Good lu
I solved it. Strangenly enough the versions of PgAccess included in
Postgress and the one you can download from it homepage both claim to
be 0.98.7, although they are different.
As you said, the one bundled with Postgres does show the views.
Thanks!
Fernando Schapachnik writes:
> Any idea
En un mensaje anterior, Tom Lane escribió:
> Fernando Schapachnik <[EMAIL PROTECTED]> writes:
> > Any idea why Views do not show up in PgAccess Views tab
> > (Postgres 7.1.2, PgAccess 0.98.7)? Any idea on how to solve it?
>
> Are you *sure* you are using the up-to
Hi,
I'm reposting it here because haven't found an answer on
-interfaces. Hope to have more luck :)
I wonder if somebody has a clue on this, because I'm lost.
I was having problems with TCL 8.3 and encoding. Tatsuo Ishii
was kind enough to provide me with the necessary
En un mensaje anterior, Tatsuo Ishii escribió:
> > Sorry... I mean non-ASCII chars doesn't look good on PgAccess plus
> > they are stored as 'garbage' (really two characters).
>
> For Japanese, an UNICODE database and TCL 8.3 combo works well. What
> kind of charset (encoding) are you using? Can
Hello:
I'm not able to get a proper encoding with TCL 8.3
and Postgres 7.1.2_2.
I've tried setting the DB enconding to UNICODE and still
doesn't work.
If I use TCL 8.0 the chars get stored properly on the DB but
are not shown correctly on PgAccess (they are shown in hexa)
En un mensaje anterior, Tom Lane escribió:
> Fernando Schapachnik <[EMAIL PROTECTED]> writes:
> > select * from aliases where alias~'^claudia.gonzalez$' \g
> > alias|receptores
> > -+--
> > (0 rows)
>
> > select * from
Hello:
Maybe somebody could give some clue about what is happening:
I have 6.5.0 running over Solaris 2.5.1 SPARC. I have a
database with 5 tables, 3 of them < 100 regs. and 2 ("usuarios" and
"passwd") with >1. When querying for:
SELECT u.nombre_cuenta, per.nombre, pas.clav
33 matches
Mail list logo
