[GENERAL] Resetting serial type after delete from table

If I delete from table, which table contains a serial type field, and then insert new rows into the table excluding the [serial] column from the list of columns in the INSERT statement, the numbers in the serial column resume where they left off prior to the delete from table: 639, 640,

Re: [GENERAL] Resetting serial type after delete from table

On Saturday 8. May 2010 10.11.32 John Gage wrote: If I delete from table, which table contains a serial type field, and then insert new rows into the table excluding the [serial] column from the list of columns in the INSERT statement, the numbers in the serial column resume where they

Re: [GENERAL] Resetting serial type after delete from table

Thanks very, very much. I got as far as 8.1.4 and did not find 9.15. May I suggest that the documentation have an index entry under serial for 9.15, which is a major heading whereas 8.1.4 is a minor heading and has its own index entry? This is said from the perspective of awe for the

[GENERAL] Documentation availability as a single page of text

Is the documentation available anywhere as a single page text file? This would be enormously helpful for searching using regular expressions in Vim, for example, or excerpting pieces for future reference. John -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make

[GENERAL] Lightning Talks for PgCon! Submit yours today.

Hi! We're having Lightning Talks again at PgCon - scheduled for 5:30pm on May 20th in Ottawa! Do you have a talk or idea you'd like to share? Lightning Talks are one of the most highly attended sessions because they are fast, fun, and useful (but not always). Slides are not required. If you use

Re: [GENERAL] psql weird behaviour with charset encodings

hernan gonzalez hgonza...@gmail.com writes: Sorry about a error in my previous example (mixed width and precision). But the conclusion is the same - it works on bytes: This example works like that because it's running in C locale always. Try something like this: #includestdio.h

[GENERAL] Invitation to connect on LinkedIn

LinkedIn Paulo moraes requested to add you as a connection on LinkedIn: -- Andrew, I'd like to add you to my professional network on LinkedIn. - Paulo Accept invitation from Paulo moraes

[GENERAL] Query Issue with full-text search

This may better-belong in pgsql-sql but since it deals with a function as opposed to raw SQL syntax I am sticking it here Consider the following DBMS schema slice Table public.post Column | Type |

[GENERAL] Database design confusing pg_restore, and misc pg_restore issues

Hey everyone, I run a website that sells videogames, and different games have different registration systems, so I have a database design that goes something like this: registration_type enum('none', 'regtype1', 'regtype2') products(product_id, registration_type) order_item(order_id,

Re: [GENERAL] psql weird behaviour with charset encodings

Wow, you are right, this is bizarre... And it's not that glibc intends to compute the length in unicode chars, it actually counts bytes (c plain chars) -as it should- for computing field widths... But, for some strange reason, when there is some width calculation involved it tries so parse the

Re: [GENERAL] Documentation availability as a single page of text

John Gage wrote: Is the documentation available anywhere as a single page text file? This would be enormously helpful for searching using regular expressions in Vim, for example, or excerpting pieces for future reference. Uh, no, and no one has ever asked for that. There must be some

Re: [GENERAL] Documentation availability as a single page of text

Bruce Momjian wrote: John Gage wrote: Is the documentation available anywhere as a single page text file? This would be enormously helpful for searching using regular expressions in Vim, for example, or excerpting pieces for future reference. Uh, no, and no one has ever asked

[GENERAL] Query that produces index information for a Table

Hello All, I am trying to pull together some general information about indices (indexes?) for a particular table. I need the following: Index Name, Table Name, Column Name, Unique/Non-Unique, and ordinal position in the index. The information_schema.key_column_usage gets me most of the way

Re: [GENERAL] Query that produces index information for a Table

Boyd, Craig cr...@mysoftforge.com writes: I am trying to pull together some general information about indices (indexes?) for a particular table. I need the following: Index Name, Table Name, Column Name, Unique/Non-Unique, and ordinal position in the index. The

Re: [GENERAL] psql weird behaviour with charset encodings

hernan gonzalez hgonza...@gmail.com writes: BTW, I understand that postgresql uses locale semantics in the server code. But is this really necessary/appropiate in the client (psql) side? Couldnt we stick with C locale here? As far as that goes, I think we have to turn on that machinery in

Re: [GENERAL] Database design confusing pg_restore, and misc pg_restore issues

Rick Yorgason r...@longbowgames.com writes: In other words, (order_id, product_id) of order_item is a foreign key to either reginfo1, reginfo2, or nothing, depending on which product it is. I think you'll find that few people regard that as good database design. The works really well, until

Re: [GENERAL] Database design confusing pg_restore, and misc pg_restore issues

On 08/05/2010 10:33 PM, Tom Lane wrote: Since you say that --disable-triggers doesn't help, I guess that you're applying that function not in a trigger but in a CHECK constraint? That's pretty horrid in itself: CHECK is *not* meant to enforce anything except local properties of the newly